ci: pin npm major in release workflow#86
Merged
Conversation
`npm install -g npm@latest` fails since npm@12 requires Node >=22.22.2, newer than the pinned NODE_VERSION (22.12.0), breaking all releases (first failure: run 29867901325). Pin to npm@11 so `latest` drift cannot break the release pipeline. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
AaronDDM
approved these changes
Jul 21, 2026
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.
Problem
The Release workflow failed on the
@nylas/react3.2.13 release (run 29867901325):npm install -g npm@latestnow resolves to npm@12, which requires a newer Node than the pinnedNODE_VERSION(22.12.0). Every release fails until this is fixed — deterministic, not flaky.Fix
Pin the npm major (
npm@11) solatestdrift can't break releases. Alternative considered: bumping theNODE_VERSIONrepo variable — that also works but changes the build/publish runtime for all jobs and only defers the nextlatestbreakage.Context
This is blocking the release of
@nylas/react@3.2.13(#85 — web-elements 2.5.15 with the HeliosX Scheduler Editor availability fixes, nylas/nylas#957 + #958). Once merged, the Release workflow needs a re-run on main to resume the changesets flow.🤖 Generated with Claude Code