Skip to content

fix(release): drop repeated changelog entries on release PRs - #36

Merged
bnb merged 1 commit into
mainfrom
bnb/release-changelog-dupes
Nov 5, 2026
Merged

bnb merged 1 commit into
mainfrom
bnb/release-changelog-dupes

Conversation

@botandbang

Copy link
Copy Markdown
Contributor

uppt lists every commit since the last tag and has no setting to leave any out. 14 commits reached main twice under different hashes, because GitHub rebased stacked PRs as their bases merged while the branches above kept the old commits (for example 38b25ea). So #30's changelog has 107 entries for 93 changes.

Added: tools/release-pr-changelog.mjs, which removes commit entries that repeat within a section from open release/v* PRs, and its tests. Added a changelog-pr job to release.yml that runs it after uppt/pr, with pull-requests: write.

Changed: tools/coverage.sh runs the new tests, and the README mentions the step.

The first entry listed is the one kept. After each push to main the body can show repeats until this job finishes.

uppt lists every commit since the last tag and has no setting to leave any out, so the 14 commits that reached main under two hashes are listed twice on the v0.2.0 release PR. GitHub rebased stacked PRs as their bases merged while the branches above kept the old commits. A job after uppt/pr now removes the repeats from the PR body.
@bnb
bnb merged commit 50c23e4 into main Nov 5, 2026
11 checks passed
@bnb
bnb deleted the bnb/release-changelog-dupes branch November 5, 2026 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants