fix(ci): run release on Node 24, drop broken npm@latest upgrade - #4
Merged
Conversation
Same fix as openeudi/openid4vp and openeudi/core: `npm install -g npm@latest` pulls npm@12, which fails EBADENGINE on Node 20 and (on Node 24) ships a global install missing `sigstore`, breaking `npm publish --provenance`. Node 24's bundled npm handles trusted publishing, so bump setup-node to 24 and remove the upgrade step. Prevents the next release from failing. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Preemptive fix mirroring openeudi/openid4vp#26+#27 and openeudi/core#9. The release workflow pins Node 20 +
npm install -g npm@latest; npm@12 failsEBADENGINEon Node 20 and (on Node 24) its global install is missingsigstore→npm publish --provenanceMODULE_NOT_FOUND. Bump to Node 24 and drop the upgrade step so the nextdcqlrelease doesn't break.