fix: keep first release changelog canonical - #69
Merged
Conversation
This was referenced Aug 31, 2026
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\n\n- keep the pre-first-release changelog empty so release-please creates the single canonical # Changelog header\n- prevent release-please from demoting an existing header into a stray ## Changelog section\n- preserve regression checks against versioned Unreleased headings and nested changelog headers\n\n## Why\n\nThe current release-please updater only recognizes version headings containing a digit. With non-version content in the pre-release file, its first-release path prepends a new header and demotes the existing header, which produced an extra ## Changelog in PR #66.\n\n## Verification\n\n- pnpm test — 55 files, 600 passed, 6 skipped\n- pnpm typecheck\n- pnpm lint\n- pnpm audit --audit-level=low — no known vulnerabilities\n- pnpm install --frozen-lockfile\n- git diff --check\n\nThis PR only corrects release metadata generation. It does not publish npm, create tags, or create a GitHub Release.