Repository navigation
Cut 1.15.0/1.15.1 headings in CHANGELOG and merge duplicate subsections - #353
Merged
Merged
Conversation
…ctions The entries shipped in v1.15.0 (tagged 2026-09-19) move under their own heading, v1.15.1 (tagged 2026-09-26, a version-only change) gets one, and only post-release entries stay under [Unreleased]. Duplicate Added / Changed / Fixed subsections are merged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Member
Author
|
Self-review rubric (head of
Out-of-diff observation: This review was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener). drafted by Claude on behalf of Daniel Stephenson |
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
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.
Summary
## [1.15.0] – 2026-09-19heading. The set of entries was taken fromCHANGELOG.mdat thev1.15.0tag (release commit 21132ed, chore: release 1.15.0 #343), and the date is that commit's date. Every bullet there matches a bullet that was under[Unreleased]onmain.## [1.15.1] – 2026-09-26heading is added.git diff v1.15.0 v1.15.1touches only the<version>inpom.xml, so the entry states that only the version number changed.v1.15.1stay under[Unreleased]: the test suite, trace-client 0.3.0 and trace-client 0.4.0.### Added/### Changed/### Fixedsubsections are merged and ordered Added → Changed → Fixed. The duplicate### Changedin[2.0.0-SNAPSHOT-8-8-2026]is merged the same way.No bullet text was removed or rewritten apart from that wording change. A script compared the bullets before and after and found no other difference.
Not changed:
[2.0.0-SNAPSHOT-8-8-2026]stays where it is in the file. How that snapshot line should be ordered against the 1.15.x releases is the maintainer's call, as the issue notes. It is recorded here as an open question and is not decided by this PR.Test plan
HEAD:CHANGELOG.mdandv1.15.0:CHANGELOG.md(script-verified)grep -n '^##' CHANGELOG.mdshows no duplicate subsection under any release headingCloses #346
Other open issues were not picked up this cycle. #342 is done on the external download listings, not in this repository. #303, #304, #305, #302, #292, #283, #282, #281, #280, #265 and #264 are feature requests or larger work, beyond a documentation-sized cycle.
This PR description was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).
🤖 Generated with Claude Code
drafted by Claude on behalf of Daniel Stephenson