Skip to content

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

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#3
OussemaFr merged 1 commit into
mainfrom
chore/bust-pypi-badge-v0.1.1

Conversation

@OussemaFr

@OussemaFr OussemaFr commented Jun 22, 2026

Copy link
Copy Markdown
Member

What

Same one-line fix as SocialAPIsHub/socialapis-python#9 and SocialAPIsHub/facebook-scraper-python#4 — forces GitHub's Camo image proxy to re-fetch the PyPI version badge by changing the URL.

Why

PyPI has v0.1.1; `shields.io` returns `v0.1.1`; README 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`

Test plan

After merging:

  • Hard-refresh the repo home page
  • Badge shows `PyPI v0.1.1`

Same fix as the other two SocialAPIsHub repos: 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.

cacheSeconds=300 added so shields.io itself caches for only 5
min going forward, limiting future drift after v0.1.2.
@OussemaFr OussemaFr merged commit 6bd4004 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