Skip to content

fix(ci): float release Node version to satisfy npm's engine requirement - #412

Merged
Vimlesh-Kumar merged 1 commit into
hiddentao:masterfrom
papandreou:fix-release-node-version
Aug 8, 2026
Merged

Vimlesh-Kumar merged 1 commit into
hiddentao:masterfrom
papandreou:fix-release-node-version

Conversation

@papandreou

Copy link
Copy Markdown
Contributor

Summary

  • The release workflow (failed run: https://github.com/hiddentao/squel/actions/runs/31253577777/job/93093528658#step:6:1) pins Node to 22.14.0, but npm install -g npm@latest now installs npm 12.0.2, which requires Node ^22.22.2 || ^24.15.0 || >=26.0.0. That mismatch fails with EBADENGINE before publishing can happen.
  • Change node-version to "22" so actions/setup-node always resolves the latest 22.x patch release, which satisfies npm 12s engine requirement now and going forward.

Test plan

  • Merge and confirm the next Release workflow run gets past the npm install -g npm@latest step

npm 12.0.2 now requires Node ^22.22.2 || ^24.15.0 || >=26.0.0, so the
release workflow's pinned 22.14.0 fails "npm install -g npm@latest"
with EBADENGINE. Use "22" so setup-node always resolves the latest
22.x patch.
@Vimlesh-Kumar
Vimlesh-Kumar merged commit 862a8f7 into hiddentao:master Aug 8, 2026
2 checks passed
@Vimlesh-Kumar

Copy link
Copy Markdown
Collaborator

@papandreou Thanks for the fix! Version 6.4.0 has now been successfully released.

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