Repository navigation
Prepare release 0.5.0 - #110
Conversation
Move everything under [Unreleased] in CHANGELOG.md into a dated 0.5.0 section and raise the product version to 0.5.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Release 0.5.0, the owner's decision.
Directory.Build.props: version 0.5.0.CHANGELOG.md: everything under [Unreleased] moved under## [0.5.0] - 2026-11-03. The date is the day of the tag - if the tag falls on another day, the heading is corrected before it.The minor number moves because snapshots are now schema version 7. This version still reads snapshots of versions 4 to 6, and the changelog says so.
Checked locally: the two tag gates of
release.yml(the tag and the version file agree, the changelog is closed for this version) pass forv0.5.0, run from the workflow's own text. Their self-test turns both red for a tag that is not the version and the changelog gate red for an entry left under [Unreleased]. A build of this tree answersbws --versionwithbws 0.5.0.Before the tag: the gate on this tree, a manual run of the mutation workflow on this commit, the rehearsal on a throwaway machine with a candidate built from the merge commit and compared against 0.4.0, and a green build on that commit.
This release is the first one with an MSI installer. No dry run of the build phase of
release.ymlwas made for it, so the first run of that phase with the installer is the one on the tag.🤖 Generated with Claude Code
Summary by CodeRabbit