Cut v1.2.0 in the changelog - #15
Merged
Merged
Conversation
Moves the overhaul entries from [Unreleased] into a dated 1.2.0 heading now that #13 is merged, and notes that cutting a release also means publishing a matching GitHub Release — the repo had tags with no release behind them, which is how v1.0.0 stayed marked Latest for eight months. 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.
Follows #13. Moves the overhaul entries out of
[Unreleased]into a dated[1.2.0]heading, linked back to #11 and #13.Also amends the versioning instructions to say that cutting a release means publishing a GitHub Release alongside the tag. The repo had drifted the other way —
v1.0.0was still marked Latest eight months and two releases later, because tags were being cut without releases behind them.v1.1.0has now been published to match its tag.Once this merges I'll tag
v1.2.0onmainand publish its release, so the tag points at a commit whose changelog already reads 1.2.0 rather than "Unreleased".🤖 Generated with Claude Code