Skip to content

docs: add duplicate-changelog-entry check to release PR review steps #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
twada merged 1 commit into from
Aug 25, 2026
Merged

docs: add duplicate-changelog-entry check to release PR review steps #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,14 @@ Released packages: `@power-assert/transpiler-core`, `@power-assert/transpiler`,
links (a wrong major bump or a `v0.0.0`-based compare link means tag
matching is broken), and always review the diff of `.github/workflows` and
lockfiles before approving anything.
Also check the CHANGELOGs for **duplicate entries**: when a merged PR's
title is in Conventional Commits form, GitHub's merge commit carries that
title in its body, and release-please may extract it as an extra entry
alongside the PR's actual commits (observed with PR #42, where the merge
commit produced a second `fix:` entry; the trigger conditions are not fully
understood, so check every release). Remove the duplicate — the entry
linking the merge commit — by hand-editing the release PR per the
CHANGELOG policy above.
2. **Approve the `npm` environment deployment**
(Actions → the waiting Release run → Review deployments → `npm`).
3. The publish job runs `npm ci --ignore-scripts`, `npm run build:dist`,
Expand Down