fix: pin conventional-changelog-conventionalcommits to avoid writer conflict - #268
Merged
Merged
Conversation
…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
marked this pull request as ready for review
August 21, 2026 23:42
cdmren
enabled auto-merge
August 21, 2026 23:43
joris974
approved these changes
Aug 24, 2026
joris974
left a comment
joris974
left a comment
Member
There was a problem hiding this comment.
We can pin at ^9 to avoid bumping all the time https://github.com/freckle/parser-js/pull/267/changes
This was referenced Aug 26, 2026
Merged
joris974
added a commit
to freckle/haskell-cli-template
that referenced
this pull request
Aug 26, 2026
…onflict (#33) The preset floats to 10.x, which requires conventional-changelog-writer@9. cycjimmy/semantic-release-action@v6.0.0 runs semantic-release@25, whose @semantic-release/release-notes-generator@14 still resolves writer@8, so releases die with `Missing helper: "..."`. Holds it at 9.3.1, matching freckle/parser-js#268. Templates especially, since every repo generated from one inherits the bare entry. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This was referenced Aug 26, 2026
joris974
added a commit
that referenced
this pull request
Aug 27, 2026
…ajor #268 pinned the exact patch, 9.3.1. Pinning the major keeps patch and minor releases flowing while still excluding 10.x, which requires conventional-changelog-writer@9+ that the bundled @semantic-release/release-notes-generator does not provide. Matches maybe-js and ajax-js.
joris974
added a commit
that referenced
this pull request
Aug 28, 2026
…ajor #268 pinned the exact patch, 9.3.1. Pinning the major keeps patch and minor releases flowing while still excluding 10.x, which requires conventional-changelog-writer@9+ that the bundled @semantic-release/release-notes-generator does not provide. Matches maybe-js and ajax-js.
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
2 participants
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.
Previous fix for the release didn't work 😬
AI Slop
The Release workflow's
generateNotesstep was failing withMissing helper: "conventional-changelog-conventionalcommits requires conventional-changelog-writer@9 or newer...". Theextra_pluginsinput installsconventional-changelog-conventionalcommitsunpinned, which now resolves to 10.x — a release that switched to a template engine requiringconventional-changelog-writer@9+.@semantic-release/release-notes-generator(bundled bycycjimmy/semantic-release-action@v6.0.0) still pinsconventional-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_pluginsinto onenode_modules) against a real clone of this repo with a local bare remote standing in for GitHub, then runningsemantic-release --dry-run. With the unpinned preset it reproduced the identical CI error; with the pin,generateNotescompleted and produced a correct rendered changelog.