fix(ci): Node 22 for release — npm@latest now requires >=22 - #21
Merged
Merged
Conversation
The release run on main failed at 'Upgrade npm': npm@12.0.1 requires Node ^22.22.2+, but the workflow pinned Node 20 (from the OIDC provenance fix era). Node 20 is also deprecated on GitHub runners. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
alec-bell
approved these changes
Jul 21, 2026
Contributor
|
🎉 This PR is included in version 1.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
2 participants
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 Release run for #20 (merge
8ae7e53) failed at the 'Upgrade npm' step:npm@latestis now 12.0.1, which requires Node ^22.22.2+, while the workflow pinned Node 20 (from the OIDC provenance fix). Node 20 is also being deprecated on GitHub runners. Bumps setup-node to 22 with a comment so the next npm major doesn't silently strand releases again.After merge, the push to main re-triggers Release — which should publish the per-session overrides feature (#20) as the next version.
🤖 Generated with Claude Code