fix(release): align latest-release metadata across release surfaces (sy-3aj)#526
Merged
Conversation
…sy-3aj) A v1.5.3 dogfood found the public "latest version" surfaces disagreeing: PyPI=1.5.3, GitHub releases/latest=v1.0.3, tags up to v1.5.3, site=v1.4.0. Operational fix (done out-of-band, not in this diff): backfilled the missing GitHub Releases for the contiguous v1.x gap (v1.0.4 → v1.5.3) with --generate-notes, marking only v1.5.3 as latest. GitHub releases/latest now equals the PyPI version. The live site already serves v1.5.3 (auto-tag.yml re-renders site artifacts on each bump), so the v1.4.0 hero text self-resolved when v1.5.3 shipped. Durable fixes in this PR: - docs/RELEASING.md: add a "Post-release verification" checklist that checks all four surfaces (PyPI, GitHub releases/latest, tag↔release gap, synthpanel.dev) after every release, plus a backfill recipe for when releases/latest lags PyPI. - site/generate-og-image.py: read the version from __version__.py instead of hardcoding it (it had drifted to "v0.9.1"); regenerate og-image.png and github-social-preview.png so the social cards read v1.5.3. Closes #524 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.
Summary
A v1.5.3 dogfood found the public "latest version" surfaces disagreeing:
PyPI=1.5.3, GitHub releases/latest=v1.0.3, tags up to v1.5.3,
site=v1.4.0.
Operational fix (done out-of-band, not in this diff): backfilled the
missing GitHub Releases for the contiguous v1.x gap (v1.0.4 → v1.5.3)
with
--generate-notes, marking only v1.5.3 as latest. GitHubreleases/latestnow equals the PyPI version. The live site alreadyserves v1.5.3 (
auto-tag.ymlre-renders site artifacts on each bump),so the v1.4.0 hero text self-resolved when v1.5.3 shipped.
Durable fixes (in this PR)
docs/RELEASING.md: add a "Post-release verification" checklist that checks all four surfaces (PyPI, GitHubreleases/latest, tag↔release gap, synthpanel.dev) after every release, plus a backfill recipe for whenreleases/latestlags PyPI.site/generate-og-image.py: read the version from__version__.pyinstead of hardcoding it (it had drifted to "v0.9.1"); regenerateog-image.pngandgithub-social-preview.pngso the social cards read v1.5.3.Test plan
site-cli-syncdrift check is the relevant gate for the regenerated PNGs).References