I recently created a package candidate for cql-io. I found a few places where the exception handling needed to be improved.
In reviewing the candidate, I found some additional things I would like to change. I uploaded the modified sources. I would like to announce the candidate and hopefully get users to test it in the wild.
I’m running into a problem: If I browse to an individual file I get the newly uploaded sources.
But if I request the .tar.gz I get the original upload. This is preventing me from announcing the candidate. I want to ensure that if people test the candidate, they are testing what will be released. Even if it’s just me pointing my build system to the candidate instead of to a local file.
Do I just need to contact a hackage admin and ask them to clear the cache for that entry from the CDN that is fronting hackage?
Is this a bug in hackage? Presumably if hackage served candidates with “ETAG” headers and reasonable cache controls, this would sort itself automatically.