Skip to content

fix: pin conventional-changelog-conventionalcommits to avoid writer conflict - #268

Open
cdmren wants to merge 1 commit into
mainfrom
cdm/fix-semantic-release-writer-conflict
Open

fix: pin conventional-changelog-conventionalcommits to avoid writer conflict#268
cdmren wants to merge 1 commit into
mainfrom
cdm/fix-semantic-release-writer-conflict

Conversation

@cdmren

@cdmren cdmren commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Previous fix for the release didn't work 😬

AI Slop

The Release workflow's generateNotes step was failing with Missing helper: "conventional-changelog-conventionalcommits requires conventional-changelog-writer@9 or newer...". The extra_plugins input installs conventional-changelog-conventionalcommits unpinned, which now resolves to 10.x — a release that switched to a template engine requiring conventional-changelog-writer@9+. @semantic-release/release-notes-generator (bundled by cycjimmy/semantic-release-action@v6.0.0) still pins conventional-changelog-writer@^8.0.0, so the two conflict.

Pinned the preset to 9.3.1, the last release before that requirement was introduced.

Verified by reproducing the exact install topology the action uses (installing semantic-release + extra_plugins into one node_modules) against a real clone of this repo with a local bare remote standing in for GitHub, then running semantic-release --dry-run. With the unpinned preset it reproduced the identical CI error; with the pin, generateNotes completed and produced a correct rendered changelog.

…onflict

The unpinned preset resolved to 10.x, which requires
conventional-changelog-writer@9+, while @semantic-release/release-notes-generator
still pins writer@^8. Pinning to 9.3.1, the last release before that
requirement, avoids the conflict.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@cdmren
cdmren marked this pull request as ready for review August 21, 2026 23:42
@cdmren
cdmren requested a review from a team as a code owner August 21, 2026 23:42
@cdmren
cdmren enabled auto-merge August 21, 2026 23:43
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.

1 participant