ci: fix npm publish job broken by npm 12's Node engine requirement - #124
Merged
rbuchmayer-pplx merged 1 commit intoJul 27, 2026
Merged
Conversation
npm@latest (12.x) now requires Node >= 22, so the publish job's npm upgrade step fails on Node 20 before publishing. Bump the job to Node 24 and pin the npm upgrade to the 12.x major so future engine-floor bumps in npm cannot break the release path again. The npm upgrade step stays: trusted publishing (OIDC) requires npm >= 11.5, newer than Node's bundled npm.
rbuchmayer-pplx
marked this pull request as ready for review
July 27, 2026 17:50
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.
The publish workflow failed before publishing anything: the "Get latest npm" step installs npm@latest, and npm 12 now requires Node >= 22 while the job runs Node 20.
No package code changes. After merge, the 1.0.0 release can be retried via workflow_dispatch.