release: pin npm to 11.x so publish works on node 20 runner#93
Merged
Conversation
npm@latest is now 12.0.1, which requires node >= 22 and aborts with EBADENGINE on this workflow's node 20 runner, failing the 1.6.0 publish before it starts. Pin npm@11 — still >= 11.5.1 for OIDC trusted publishing and compatible with node 20. 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
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.
npm@latest is now 12.0.1 (requires node >= 22) and aborts with EBADENGINE on the release workflow's node 20 runner, which failed the 1.6.0 publish. Pin npm@11 — still >= 11.5.1 for OIDC trusted publishing, node-20 compatible. CI-only change.
After merge, the 1.6.0 publish is re-triggered via workflow_dispatch (this PR does not change package.json, so it will not auto-trigger release.yml).
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com