Skip to content

ci: pin npm major in release workflow#86

Merged
maithri471 merged 1 commit into
mainfrom
fix/release-workflow-npm-pin
Jul 21, 2026
Merged

ci: pin npm major in release workflow#86
maithri471 merged 1 commit into
mainfrom
fix/release-workflow-npm-pin

Conversation

@maithri471

Copy link
Copy Markdown
Contributor

Problem

The Release workflow failed on the @nylas/react 3.2.13 release (run 29867901325):

npm error engine Not compatible with your version of node/npm: npm@12.0.1
npm error notsup Required: {"node":"^22.22.2 || ^24.15.0 || >=26.0.0"}
npm error notsup Actual:   {"npm":"10.9.0","node":"v22.12.0"}

npm install -g npm@latest now resolves to npm@12, which requires a newer Node than the pinned NODE_VERSION (22.12.0). Every release fails until this is fixed — deterministic, not flaky.

Fix

Pin the npm major (npm@11) so latest drift can't break releases. Alternative considered: bumping the NODE_VERSION repo variable — that also works but changes the build/publish runtime for all jobs and only defers the next latest breakage.

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

`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>
@maithri471
maithri471 requested review from a team and radenkovic as code owners July 21, 2026 21:04
@maithri471
maithri471 requested a review from b3ndoi July 21, 2026 21:04
@maithri471
maithri471 merged commit 78017a3 into main Jul 21, 2026
5 checks passed
@maithri471
maithri471 deleted the fix/release-workflow-npm-pin branch July 21, 2026 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants