Date 1.1.0 to the day it ships, and give it a link reference - #9
Merged
Conversation
Two things a release notices and nothing else does. The heading said 2026-08-25 because that is when the entry was written, not when it ships. And `[1.1.0]` had no link definition at the foot of the file, so the version number in the heading rendered as literal brackets on GitHub while every other release in the file linked to its compare view. `[Unreleased]` now compares against v1.1.0 rather than v1.0.0, which is what makes the next release's diff the right one. 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.
Two things a release notices and nothing else does. Both are in the changelog, and both are visible in published output.
[1.1.0]had no link definition at the foot of the file. Every other release inCHANGELOG.mdlinks to its compare view; this one rendered as literal brackets — on GitHub, and on the generated/changelog/page and its Atom feed, which are built from the same file.The heading said 2026-08-25, which is when the entry was written rather than when it ships.
[Unreleased]now compares againstv1.1.0instead ofv1.0.0, which is what makes the next release's diff the right one.The
site/changes are the regenerated changelog page and feed —pnpm site:checkfails if they are not rebuilt.This wants to land before
v1.1.0is tagged.🤖 Generated with Claude Code