Skip to content

ci: publish on Node 24 with a pinned npm - #36

Merged
JohnMcLear merged 1 commit into
mainfrom
ci/fix-publish-node
Sep 21, 2026
Merged

JohnMcLear merged 1 commit into
mainfrom
ci/fix-publish-node

Conversation

@JohnMcLear

Copy link
Copy Markdown
Member

.github/workflows/npmpublish.yml ran the publish job on Node 25, which npm 12 does not support — it requires Node ^22.22.2 || ^24.15.0 || >=26.0.0, so any npm upgrade on this runner dies with EBADENGINE:

npm error code EBADENGINE
npm error Not compatible with your version of node/npm: npm@12.0.2
npm error Required: {"node":"^22.22.2 || ^24.15.0 || >=26.0.0"}
npm error Actual:   {"node":"v25.9.0","npm":"11.12.1"}

This workflow is the older token-based publish shape, so it has no npm install -g step to pin — only the Node line is moved to 24, an LTS line supported by every npm 11.x and 12.x. This keeps it consistent with the fleet-wide fix (pilot: ether/ep_align#227) and off a Node line npm has already dropped.

🤖 Generated with Claude Code

https://claude.ai/code/session_013S4pYSjwUsiZtdtMMpW7bw

The publish workflow ran on Node 25, which npm 12 does not support: it
requires Node `^22.22.2 || ^24.15.0 || >=26.0.0`, so any npm upgrade on
this runner dies with EBADENGINE:

    npm error code EBADENGINE
    npm error Not compatible with your version of node/npm: npm@12.0.2
    npm error Required: {"node":"^22.22.2 || ^24.15.0 || >=26.0.0"}
    npm error Actual:   {"node":"v25.9.0","npm":"11.12.1"}

Move to Node 24, an LTS line supported by every npm 11.x and 12.x. This
matches the fleet-wide fix applied to the other ether/* plugin publish
workflows.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013S4pYSjwUsiZtdtMMpW7bw
@qodo-code-review

Copy link
Copy Markdown

ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing

@qodo-free-for-open-source-projects

Copy link
Copy Markdown

PR Summary by Qodo

Run npm publishing on Node 24 LTS

🐞 Bug fix ⚙️ Configuration changes 🕐 Less than 5 minutes

Grey Divider

AI Description

• Moves npm publishing from unsupported Node 25 to Node 24 LTS.
• Prevents npm 12 upgrades from failing with EBADENGINE.
High-Level Assessment

Using Node 24 is the appropriate fix because it is an LTS release compatible with npm 11 and 12 while preserving the existing token-based publish flow. Node 22 was considered but offers a shorter remaining support window, and explicitly installing npm would add unnecessary workflow complexity.

Files changed (1) +3 / -1

Bug fix (1) +3 / -1
npmpublish.ymlPublish packages with Node 24 LTS +3/-1

Publish packages with Node 24 LTS

• Changes the npm publish runner from Node 25 to Node 24 to maintain compatibility with npm 11 and 12. Adds comments documenting the relevant npm 12 engine requirements.

.github/workflows/npmpublish.yml

@qodo-free-for-open-source-projects

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can add REVIEW.md to your repo root and Qodo follows it on every PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@JohnMcLear
JohnMcLear merged commit 27f8993 into main Sep 21, 2026
3 checks passed
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.0.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant