Skip to content

release: re-release v0.5.0 with tools/release_notes.py (#391) #392

Closed

Description

@homer6

The owner asked to include #391 (tools/release_notes.py, #390) in v0.5.0, as v0.4.0 was re-released for #350.

  • Notes: a "Re-released" note in docs/releases/v0.5.0.md and a What's new entry for build(release): tools/release_notes.py for GitHub release text #391, on a PR into dev.
  • Release PR dev → main, with the owner's verdict.
  • 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.

Activity

  1. self-assigned this
    on Nov 4, 2026
  2. homer6 commented on Nov 4, 2026

    @homer6
    OwnerAuthor

    Delivered in #393.

    What changed

    Why

    Still open

  3. homer6 commented on Nov 4, 2026

    @homer6
    OwnerAuthor

    Merged in #393 (24075c7). Nothing changed since the PR opened. Next: the release PR, the tag move and the GitHub release update.

  4. homer6 commented on Nov 4, 2026

    @homer6
    OwnerAuthor

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions