ci: bump pinned Node to 22.22.2 to fix npm@latest EBADENGINE

[willwashburn]

What

Bumps the pinned Node version in .github/workflows/publish-npm.yml from 22.14.0 to 22.22.2 (all three setup-node steps).

Why

The publish workflow run failed on every publish job at the Update npm for OIDC support step:

npm error code EBADENGINE
npm error engine Not compatible with your version of node/npm: npm@12.0.0
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 install -g npm@latest now resolves to npm@12.0.0, whose engines field requires Node ^22.22.2 || ^24.15.0 || >=26. The workflow pinned Node 22.14.0, which is below the new 22.x floor, so npm refused to install with EBADENGINE. Nothing in the source changed — a new npm major raised its minimum Node requirement.

Fix

Bumping the Node pin to 22.22.2 satisfies npm 12's engine requirement while keeping npm@latest (needed for OIDC provenance / trusted publishing). This stays within the same Node 22.x major line, so it's a low-risk change. Two alternatives — pinning npm@11 or dropping the upgrade step — were rejected because the step deliberately wants a recent npm for OIDC support.

🤖 Generated with Claude Code

---

Generated by Claude Code

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[coderabbitai]

Warning

Review limit reached

@willwashburn, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 50 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 25161e3a-5c0c-47ff-8e0a-4526e9b5d068

📥 Commits

Reviewing files that changed from the base of the PR and between baa4333 and 4fd2177.

📒 Files selected for processing (1)

• .github/workflows/publish-npm.yml

📝 Walkthrough

Walkthrough

The publish-npm.yml GitHub Actions workflow is updated to use Node.js version 22.22.2 instead of 22.14.0 in three separate actions/setup-node@v4 steps across the build, publish-packages, and publish-single jobs.

Changes

Workflow Node.js Version Update

Layer / File(s)	Summary
Node.js version bump across jobs .github/workflows/publish-npm.yml	Updates Node.js version from 22.14.0 to 22.22.2 in the build, publish-packages, and publish-single job's setup-node steps.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

A hop, a skip, a version raised,
22.22.2 now amazed,
Three jobs updated, clean and neat,
This bunny's workflow can't be beat! 🐰
Off to publish, quick and sweet.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the main change: bumping the pinned Node version to resolve the npm EBADENGINE failure.
Description check	✅ Passed	The description directly explains the Node bump, the workflow failure, and the npm engine requirement.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/relaycast-workflow-failure-gmn5u2

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[cubic-dev-ai]

All reported issues were addressed across 1 file

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[willwashburn]

Good catch — the regression is real. Node 22.22.2's toolcache build ships a broken bundled npm 10.9.7 (missing promise-retry), so npm install -g npm@latest would fail with MODULE_NOT_FOUND (nodejs/node#62425, actions/runner-images#13883).

I went with a cleaner fix than the two-step workaround: pinning Node 22.22.3 instead. It bundles npm 10.9.8, which fixes the module tree at the source, still satisfies npm@12's ^22.22.2 engines requirement, and keeps the single npm install -g npm@latest step intact for OIDC provenance — no fragile npm@^10 && npm@latest bootstrap needed. Pushed in 4fd2177.

---

Generated by Claude Code