fix(sdk-ci): pin npm@11 for publish workflows (Node 20 runners)#227
Merged
Conversation
npm@12 (latest as of 2026-07-08) requires Node >=22, but the publish runners are on Node 20, so `npm install -g npm@latest` now fails with EBADENGINE. Pin to npm@11 (the newest npm that still supports Node 20) in both the preview and manual publish workflows. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
🚀 Package Preview Available!Install this PR's preview build with npm: npm i @base44-preview/sdk@0.8.37-pr.227.6e9ea56Prefer not to change any import paths? Install using npm alias so your code still imports npm i "@base44/sdk@npm:@base44-preview/sdk@0.8.37-pr.227.6e9ea56"Or add it to your {
"dependencies": {
"@base44/sdk": "npm:@base44-preview/sdk@0.8.37-pr.227.6e9ea56"
}
}
Preview published to npm registry — try new features instantly! |
ImriKochWix
approved these changes
Jul 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The publish workflows run
npm install -g npm@lateston Node 20 runners. On 2026-07-08 ~21:06 UTC, npm released npm@12.0.0, which requires Node>=22. So@latestnow resolves to npm@12 and the step fails before anything else runs:Nothing in the repo changed — the unpinned
@latestswallowed an upstream breaking major. The last successful publish (2026-07-08 ~13:56 UTC) predated npm@12 by ~7 hours.What
Pin to npm@11 — the newest npm that still supports Node 20 (
engines: ^20.17.0 || >=22.9) — in both workflows:preview-publish.yml(PR preview publish — currently red on open PRs)manual-publish.yml(publish-on-dispatch — would fail the next real publish too)Both files, because fixing only the preview would leave the actual publish broken.
Validates itself
preview-publish.ymltriggers onpull_request, so this PR runs its own pinned version — a green check here confirms the fix.Note
Pinning
npm@11is the minimal fix. Longer term, bumping the runners to Node 22 would allownpm@latestagain; out of scope here.🤖 Generated with Claude Code