fix: repair the release pipeline's changelog plugin resolution - #55
Merged
Conversation
`pnpm release` currently fails before doing anything:
ERROR The requested module '@conventional-changelog/git-client'
does not provide an export named 'isPrereleaseVersion'
@release-it/conventional-changelog@12 depends on
conventional-recommended-bump@12.1.0, which imports `isPrereleaseVersion`
from @conventional-changelog/git-client. That export only exists in
git-client 3.1.2 and later, but the lockfile resolved 3.1.0.
This repo is the only one of the group that also runs release-it-pnpm,
which pulls a second conventional-changelog stack (git-client 2.7.0 and
conventional-recommended-bump 11.2.0) alongside the first — which is what
pinned the resolution to the older version. duraflows and werken use the
same plugin without that second stack and are unaffected.
Refreshes the lockfile to git-client 3.1.2 and adds a pnpm override so a
future transitive update cannot silently reintroduce the break — the
failure only surfaces when a release is attempted, which is the worst
time to discover it.
Verified: with `pnpm install --frozen-lockfile`, a release-it dry run no
longer raises the module error and reports "Writing changelog to
CHANGELOG.md".
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JLxceiNFfXfpGoxdfQEZqw
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #55 +/- ##
=======================================
Coverage 99.85% 99.85%
=======================================
Files 11 11
Lines 668 668
Branches 153 153
=======================================
Hits 667 667
Misses 1 1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
pnpm releasein this repo currently fails before doing anything:Found while auditing the changelog-generator setup across the libraries. This is the only one of the nine where the release pipeline is broken.
Cause
@release-it/conventional-changelog@12depends onconventional-recommended-bump@12.1.0, which importsisPrereleaseVersionfrom@conventional-changelog/git-client. That export only exists in git-client 3.1.2+, but this lockfile resolved 3.1.0.Why here and not elsewhere: ziggurat is the only repo that also runs
release-it-pnpm, which pulls a second conventional-changelog stack (git-client@2.7.0,conventional-recommended-bump@11.2.0) alongside the first. That second stack is what held the resolution back.duraflowsandwerkenuse the same plugin without it and both dry-run clean — I verified each.Fix
Refreshes the lockfile to
git-client@3.1.2and adds apnpm.overridesentry so a future transitive update can't silently reintroduce it. The override is deliberate: this failure only surfaces when you attempt a release, which is the worst possible moment to find out, and the repo already usespnpm.overrideselsewhere.Lockfile +
package.jsononly — no source, config, or release-behaviour changes.Verification
Reproduced and fixed from the committed dependency state, not a loose install:
pnpm install --frozen-lockfilethen dry runisPrereleaseVersionerror, abortsWriting changelog to CHANGELOG.mdCommand used:
npx release-it 0.2.1 --ci --dry-run --no-git --no-npm --no-github.release(nothing committed, tagged, or published).🤖 Generated with Claude Code
https://claude.ai/code/session_01JLxceiNFfXfpGoxdfQEZqw