fix(ci): remove global npm upgrade from publish workflow#71
Merged
Conversation
The 'npm install -g npm@latest' step fails on Node 22.22.2 runners because the self-upgrade corrupts npm's internal dependencies (Cannot find module 'promise-retry'). Node 22 ships with npm 10.x which already supports --provenance publishing. The forced upgrade is unnecessary.
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
1 participant
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.
Problem
The publish workflow fails at the
Update npmstep with:npm install -g npm@lateston Node 22.22.2 GitHub runners corrupts npm's own internal dependencies during the self-upgrade.See: https://github.com/czottmann/linearis/actions/runs/24092632590/job/70282838576
Fix
Remove the
npm install -g npm@lateststep entirely. Node 22 ships with npm 10.x which already supports--provenancepublishing (requires npm ≥ 9.5.0). The forced global upgrade is unnecessary.After merge
Re-tag and push to re-trigger the publish:
git tag -d v2026.4.1 git push origin :refs/tags/v2026.4.1 git tag -a v2026.4.1 -m "Release 2026.4.1" git push origin v2026.4.1