chore: bust stale Camo cache showing v0.1.0 PyPI badge#9
Merged
Conversation
PyPI has v0.1.1 published; shields.io + badge.fury both correctly return v0.1.1 when queried directly. GitHub's image proxy (Camo) cached the badge.fury SVG that was first fetched before v0.1.1 landed — and Camo doesn't revalidate for hours. Fix: swap the badge URL to one Camo has never seen. New URL adds `?cacheSeconds=300` (so shields.io itself caches for only 5 min going forward, which limits future drift) plus the PyPI logo for better visual weight. No README content change beyond the badge — clicking still routes to https://pypi.org/project/socialapis-sdk/.
This was referenced Jun 22, 2026
Merged
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.
What
Forces GitHub's image proxy (Camo) to re-fetch the PyPI version badge by changing the URL to one it hasn't seen before.
Why
PyPI has v0.1.1 live:
```
$ curl -s https://pypi.org/pypi/socialapis-sdk/json | jq .info.version
"0.1.1"
$ curl -sL https://img.shields.io/pypi/v/socialapis-sdk.json | jq .message
"v0.1.1"
```
But the README badge still renders as `v0.1.0`. Cause: Camo cached the SVG fetched before v0.1.1 published and refuses to revalidate for hours.
Fix
Swap the badge URL from `badge.fury.io/py/socialapis-sdk.svg` to `img.shields.io/pypi/v/socialapis-sdk?cacheSeconds=300&label=PyPI&logo=pypi&logoColor=white`. The new URL:
Test plan
After merging: