Repository navigation
Conversation
…dded #393's changelog conflict was resolved with a pre-#392 copy of the top section, which put the eight bullets #392 had folded back under Unreleased and reverted the 0.3.0 date. Those duplicates go; the three entries new since #392 (#393's timeline fold, #394's restore guard and rustls 0.23.46) move into the matching 0.3.0 subsections; the date moves to 2026-10-17; the summary says the History tab folds quiet checks. Co-Authored-By: Claude Fable 5.1 <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
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.
What and why
#392 folded the entries merged after the 0.3.0 prepare into the 0.3.0 section and emptied Unreleased. #393's merge (
d2cff0a) undid part of that: its branch carried a pre-#392 copy ofCHANGELOG.md, and the conflict was resolved with the branch's top section, so the eight folded entries came back under Unreleased (now listed twice, once there and once under 0.3.0) and the heading's date fell back to 2026-10-06. #394 then added its two entries under Unreleased as well.This PR puts the changelog back in the shape the tag needs:
## [0.3.0]are removed from Unreleased (the Wayback redesign's three, the empty-history and version "v" fixes, and thenext,sharpandpostcss-selector-parseradvisories). Their copies under 0.3.0 are untouched.Only
CHANGELOG.mdchanges. Unreleased is empty again; no bullet appears twice in the 0.3.0 section apart from one repeat that predates all of this (macos-release.ymlnow callsscripts/fetch-node-sidecar.sh, once under 0.3.0's own Changed list and once inside the folded 0.2.0 section), left as it was.Worth a follow-up once 0.3.0 is out:
scripts/check-release.mjscould refuse a tag whoseCHANGELOG.mdstill has entries under Unreleased, which is what would have caught both this and #392's trigger before a tag.After this merges
Tag this PR's merge commit with a signed, annotated
v0.3.0from your own identity and push it. Themacos-signingenvironment still needs a required reviewer before the preflight will pass.How it was verified
pnpm test:release: 30 passed, 0 failed.releaseNotes()on the result: 6,662 characters, no em dashes; Unreleased has no body; every moved bullet is followed by one blank line and the next heading.🤖 Generated with Claude Code