chore(release): close the changelogs for 0.5.0 - #140
Merged
Conversation
0.5.0 was already opened when rc.1 was cut on 2026-08-12, so this is not a new section: the work since then is still 0.5.0, and it is folded into the section that already exists. The date moves to the day it is being cut again. Merged heading by heading rather than appended as a second block, because CHANGELOG.md may not carry two headings of the same name inside one version and a test says so. The summary at the top was written for rc.1 and described only half of what the section now holds. It leads with the signature, since that is the change a user meets first: Windows names the publisher instead of saying "Unknown publisher", and the release carries proof that can be checked without asking anyone. Co-Authored-By: Claude Opus 5 <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.
Recipe step 2, ahead of tagging
v0.5.0-rc.2.Not a new section
## [0.5.0]was opened when rc.1 was cut on 2026-08-12. The work since then is still0.5.0, so
[Unreleased]is folded into the section that already exists rather than asecond one being opened beside it, and the date moves to the day it is being cut again.
Merged heading by heading, not appended as a second block:
CHANGELOG.mdmay not carrytwo headings of the same name inside one version, and
test_the_mutable_changelog_sections_have_no_duplicate_headingssays so. The[0.5.0]section still has exactly one each of Added, Changed, Docs and Fixed.
The summary was stale
The paragraph at the top was written for rc.1 and described only the user-folder work.
It now leads with the change a user meets first - the executable is signed, so Windows
names the publisher - and says what proof ships with the release.
Checks
[Unreleased]holds zero entries and## [0.5.0] - 2026-08-19is dated, which is whatrelease.ymlrefuses to publish without.tools/release_notes.pyextracts the section (298 lines) - that text is the releasebody, so a broken section would show up on the release page.
the signal added for exactly this.
🤖 Generated with Claude Code