chore(release): bump to 0.7.0 (cb=3, refresh stuck PyPI badge)#19
Merged
Conversation
PyPI 0.6.0 page is stuck displaying v0.5.0 on its PyPI badge because its embedded README baked in `?cb=1`, which Cloudflare HIT-cached at shields.io with the then-current 0.5.0 response. Per-version PyPI descriptions are immutable, so the 0.6.0 page itself cannot be fixed. 0.7.0 bundles version bump + cb=2 -> cb=3 in one atomic PR (the sequencing the previous release-cycle missed). cb=3 is a never- queried token, so the first shields.io hit after 0.7.0 publish will fetch fresh PyPI metadata. The latest-version PyPI URL (/project/mini-antemortem-cli/) will then render correctly; the /0.6.0/ direct URL remains broken-by-design as part of the audit trail. Co-Authored-By: Claude Opus 4.7 (1M context) <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.
Why
PyPI 0.6.0 page is stuck displaying
v0.5.0on its PyPI badge.Root cause: PyPI per-version descriptions are immutable, and the 0.6.0 release shipped with
?cb=1baked into its README. Cloudflare HIT-cached thecb=1URL on shields.io while it was serving the then-current 0.5.0 response, so the 0.6.0 page is now permanently locked to that stale badge.Sequencing bug in the previous release cycle:
?cb=1to READMEcb=1baked in)?cb=2(too late — no longer reaches a PyPI release)What
Bundle version bump + cache-buster bump in one atomic PR this time:
pyproject.toml:version = "0.7.0"src/mini_antemortem_cli/__init__.py:__version__ = "0.7.0"README.md: PyPI badge?cb=2->?cb=3(cb=3is a never-queried token — guarantees fresh shields.io fetch post-publish)docs/generated/claims*.md: regenerated viascripts/generate_readme_claims.pyEffect
After 0.7.0 publish:
https://pypi.org/project/mini-antemortem-cli/(latest URL) renders 0.7.0 README withcb=3, badge shows freshv0.7.0.https://pypi.org/project/mini-antemortem-cli/0.6.0/remains broken — irreversible by PyPI design, kept as part of the audit trail (do NOT yank).Verification
python scripts/publish_readiness.py --no-network->PUBLISH_READINESS_OK no-networklocally.cb=3in wheel METADATA, wheel smoke-install, twine upload, tagv0.7.0,gh release create.Test plan
publish_readiness.py --no-network-> OKcb=3v0.7.0badge