chore(release): close the changelogs for 0.6.0 - #174
Merged
Conversation
Moves the [Unreleased] block into a dated 0.6.0 section in both changelogs and sets VERSION.txt to the number the owner named. The section is created now, at the release candidate, and serves the full release afterwards: release.yml checks a pre-release tag exactly the way it checks a final one, so -rc.1 ships the same notes. 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.
Closes the changelogs for 0.6.0 and sets
VERSION.txt, so the release candidatev0.6.0-rc.1can be tagged on master.What this commit does
[Unreleased]moves into a dated## [0.6.0] - 2026-09-03section in both changelogs,leaving the empty
## [Unreleased]header thatrelease.ymlrequires at tag time.VERSION.txtgoes from0.5.0to0.6.0.The dated section is created now, at the candidate, and serves the full release afterwards:
release.ymlchecks a pre-release tag exactly the way it checks a final one, so-rc.1shipsthe same notes. The tag carries the
-rc.1suffix, the version does not - a candidate and itsfinal release share a version by design.
What 0.6.0 contains
The full text is in
CHANGELOG.md. In short: losses that arrive in runs rather than one packetat a time, with the wireless presets tuned to match how a radio link really fails; the Control
page field search; the connections table search understanding column qualifiers and a choice of
visible columns; the Settings window; and a long list of stability fixes.
Checks
prose is a source for several of these guards and an edit after the last green run would be
unverified.
tests/test_version_and_release.py): 31 passed, including thedated-section, essay-cap, duplicate-heading and release-notes-extraction rules.
tools/release_notes.pyextracts the new section for the release page.The full rig sweep is deliberately NOT part of this: rigs are owed at a final release, not at a
candidate, and the branch name is what carries that intent.
🤖 Generated with Claude Code