docs: bust the cached PyPI badge - #2
Merged
Merged
Conversation
The version badge rendered "package or version not found" after publishing. shields had the data all along: its JSON route returned v0.1.0 while the SVG route served a cached negative, seeded when that exact URL was fetched before the package existed. cacheSeconds=300 is a new URL, so it misses the stale entry, and it caps future staleness at five minutes rather than whatever shields defaults to. A new URL also means a new camo URL, so GitHub's image proxy cannot keep serving the old one either. Applied to pyversions as well. That one renders correctly today but would go stale the same way on a change to the supported range. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The version badge renders "package or version not found" even though the package published fine.
shields had the data the whole time. Its JSON route returns the right answer while the SVG route serves a stale negative:
The negative was seeded when that exact URL was fetched before the package existed.
?cacheSeconds=300is a different URL, so it misses the stale entry, and it caps future staleness at five minutes instead of whatever shields defaults to. It also produces a new camo URL, which matters independently: GitHub's image proxy had cached the broken image too, and would have kept serving it after shields recovered.Verified both forms return
pypi: v0.1.0.Applied to
pyversionsas well. It renders correctly today (3.11 | 3.12 | 3.13 | 3.14) but would go stale the same way whenever the supported range changes.The CI badge was never broken, for the record: it returns
<title>tests - passing</title>.