You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
release: re-release v0.5.0 with tools/release_notes.py (#391) #392
Move the v0.5.0 tag from f97b4608 to the new merge commit (a tag force-push: needs the owner's yes), and update the GitHub release from tools/release_notes.py v0.5.0.
#391 changes no C++, test or workflow (a Python tool, CLAUDE.md and a README sentence), so the release's CI and local runs still hold; the tool's --self-test and the link/index checks run on the notes PR.
Re-released. #394 merged into main (bb8bd634); the v0.5.0 tag moved from f97b4608 to bb8bd634 (pushed by the owner); the GitHub release text regenerated with tools/release_notes.py v0.5.0 (rendered: 0 line breaks, the re-release quote and 3 tables): https://github.com/homer6/cpp-docs/releases/tag/v0.5.0
Activity
homer6 commentedon Nov 4, 2026
Delivered in #393.
What changed
docs/releases/v0.5.0.md: a "Re-released" note (the first tagf97b460is the same release without the script), a What's new entry for build(release): tools/release_notes.py for GitHub release text #391, and a Checks row for its self-test.docs/releases/README.md: the v0.5.0 row names the script.Why
Still open
dev→main, moving thev0.5.0tag to its merge commit (needs the owner's yes), and the GitHub release updated fromtools/release_notes.py v0.5.0.homer6 commentedon Nov 4, 2026
Merged in #393 (24075c7). Nothing changed since the PR opened. Next: the release PR, the tag move and the GitHub release update.
homer6 commentedon Nov 4, 2026
Re-released. #394 merged into
main(bb8bd634); thev0.5.0tag moved fromf97b4608tobb8bd634(pushed by the owner); the GitHub release text regenerated withtools/release_notes.py v0.5.0(rendered: 0 line breaks, the re-release quote and 3 tables): https://github.com/homer6/cpp-docs/releases/tag/v0.5.0