Skip to content

Bump pinned Node to 22.22.2 so npm@latest installs in release workflow#23

Merged
yosriady merged 1 commit into
mainfrom
fix/release-node-version
Jul 24, 2026
Merged

Bump pinned Node to 22.22.2 so npm@latest installs in release workflow#23
yosriady merged 1 commit into
mainfrom
fix/release-node-version

Conversation

@yosriady

@yosriady yosriady commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

Summary

The v1.1.0 release run failed at the "Update npm for trusted publishing" step:

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.2","node":"v22.14.0"}

npm@latest is now npm 12, which no longer supports Node 22.14.0. This bumps the pinned node-version from 22.14.0 to 22.22.2 (the minimum supported version on the 22 LTS line) in both release.yml and ci.yml, keeping the npm upgrade step for OIDC trusted publishing working and the two workflows on the same Node version.

Test plan

  • CI passes on this PR (exercises the bumped Node in ci.yml)
  • After merge, re-tag/re-run the release workflow and confirm the npm install -g npm@latest step succeeds

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

npm 12 requires Node ^22.22.2 || ^24.15.0 || >=26, so the "Update npm
for trusted publishing" step in release.yml fails with EBADENGINE on
the previously pinned 22.14.0. Bump CI to the same version to keep the
workflows consistent.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@yosriady
yosriady merged commit 5954255 into main Jul 24, 2026
6 checks passed
@yosriady
yosriady deleted the fix/release-node-version branch July 24, 2026 14:15
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.

1 participant