docs(CHANGELOG): define the [0.2.1] link, move [Unreleased] base - #10
Merged
Conversation
The 0.2.1 cut added the heading but not the link definition at the bottom, so `## [0.2.1]` rendered as literal bracketed text instead of a link to the release — and [Unreleased] still compared from v0.2.0, which would have shown the 0.2.1 changes as unreleased forever. Caught before the tag deliberately: the tag freezes whatever CHANGELOG the commit carries, and a v0.2.2 to fix two link lines is exactly the kind of version churn this release is trying not to spend. [0.1.0] stays link-less on purpose — no public tag exists for that line.
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.
Summary
The 0.2.1 cut (#9) added the
## [0.2.1]heading but not the matching linkdefinition at the bottom of the file, so it rendered as literal bracketed text
rather than a link to the release.
[Unreleased]also still compared fromv0.2.0, which would have listed the 0.2.1 changes as unreleased indefinitely.[0.1.0]stays link-less on purpose — the entry itself states no public tagexists for that line.
Why this lands before the tag
v0.2.1has not been pushed yet. The tag freezes whichever CHANGELOG thecommit carries, and correcting two link lines afterwards would cost either a
moved tag or a
v0.2.2— the exact version churn this release is trying not tospend.
Test plan
Documentation only; no code paths touched. The link targets are the standard
Keep a Changelog compare/release URLs, and
v0.2.1will exist the moment thetag is pushed (immediately after this merges).
🤖 Generated with Claude Code