chore(release): close the changelogs for 0.5.0 - #126
Merged
Conversation
- move everything under [Unreleased] into a dated [0.5.0] section in both changelogs, leaving the [Unreleased] header in place - VERSION.txt 0.4.0 -> 0.5.0, at the owner's instruction - add the short summary the release page opens with The tag for this one is v0.5.0-rc.1, a pre-release: the base has to equal VERSION.txt, and the suffix is what makes GitHub mark it as such. 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.
Release preparation for the
v0.5.0-rc.1pre-release.[Unreleased]moves into a dated[0.5.0]section in both changelogs, and the[Unreleased]header stays where it isVERSION.txtgoes 0.4.0 -> 0.5.0The tag will be
v0.5.0-rc.1. Its base has to equalVERSION.txt, and the suffix is what makes it publish as a pre-release.Why a release candidate first: the SBOM attestation step has never run. It only executes on a real tag, so this walks the whole path - build, smoke of the built executable, archive, checksums, SBOM, attestation, release - without claiming the version is final. It also gives anyone who wants it something to download.
Verified before the commit:
python -m pytest tests1119 passed,smoke_gui.pyOK, the built--versionreports 0.5.0, andtools/release_notes.py 0.5.0extracts exactly the section that will become the release body.