Skip to content

chore: bust stale Camo cache showing v0.1.0 PyPI badge#4

Merged
OussemaFr merged 1 commit into
mainfrom
chore/bust-pypi-badge-v0.1.1
Jun 22, 2026
Merged

chore: bust stale Camo cache showing v0.1.0 PyPI badge#4
OussemaFr merged 1 commit into
mainfrom
chore/bust-pypi-badge-v0.1.1

Conversation

@OussemaFr

Copy link
Copy Markdown
Member

What

Same fix as SocialAPIsHub/socialapis-python#9 — forces GitHub's Camo image proxy to re-fetch the PyPI version badge.

Why

PyPI has v0.1.1 live; `shields.io` returns `v0.1.1`; but the README badge still shows `v0.1.0` because Camo cached the SVG fetched before publication.

Fix

Badge URL: `badge.fury.io/py/socialapis-sdk.svg` → `img.shields.io/pypi/v/socialapis-sdk?cacheSeconds=300&label=PyPI&logo=pypi&logoColor=white`

The new URL is a different bytes-string → Camo treats as fresh image → refetches.

Test plan

After merging:

  • Hard-refresh the repo home page
  • Badge shows `PyPI v0.1.1`
  • Click → routes to PyPI project page

Same fix as SocialAPIsHub/socialapis-python: GitHub's Camo proxy
cached the SVG from before v0.1.1 published and won't revalidate
for hours. Swapping the badge URL to one Camo hasn't seen forces
a fresh fetch.

New URL also adds cacheSeconds=300 (so shields.io itself caches
for only 5 min going forward, limiting future drift) and the
PyPI logo for visual weight. Same target — clicking still routes
to pypi.org/project/socialapis-sdk.
@OussemaFr OussemaFr merged commit f70f556 into main Jun 22, 2026
@OussemaFr OussemaFr deleted the chore/bust-pypi-badge-v0.1.1 branch June 22, 2026 22:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant