ci: pin release to Node 24 LTS, drop npm@latest self-update (fixes sigstore publish failure) - #197
Closed
hiroTamada wants to merge 1 commit into
Closed
ci: pin release to Node 24 LTS, drop npm@latest self-update (fixes sigstore publish failure)#197hiroTamada wants to merge 1 commit into
hiroTamada wants to merge 1 commit into
Conversation
npm@latest now resolves to npm@12, which dropped Node 20 support (requires ^22.22.2 || ^24.15.0 || >=26.0.0). The release job pinned Node 20, so `npm install -g npm@latest` failed with EBADENGINE and skipped GoReleaser. Node 24 is already the actions runtime and ships npm >= 11.5.1 for OIDC trusted publishing. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
hiroTamada
marked this pull request as ready for review
July 9, 2026 15:58
hiroTamada
changed the title
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
1 participant
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.
Summary
The
Release CLIworkflow has been failing on the npm publish of@onkernel/cli. This supersedes the interim Node bump in #196.What was happening
node-version: 'latest'resolved to Node 26.5.0 (a non-LTS "Current" release).npm install -g npm@latestupgraded the global npm to 12.0.0.npm publishwith provenance (required for OIDC trusted publishing), and npm 12 fails to resolve its bundledsigstoremodule:This is a current npm bug: npm/cli#9722. The GitHub release published, but the npm publish failed.
Fix
node-versionto24(LTS). Node 24 bundles npm ≥ 11.5.1, which is the documented known-good version for npm OIDC trusted publishing and has working provenance/sigstore.npm install -g npm@lateststep — it's redundant on Node 24 and was the source of the broken npm 12.Note on re-releasing
Tag-triggered runs use the workflow file at the tagged commit. After this merges, re-cut the release tag on updated
main(delete + re-pushv0.21.0, or tag a fresh commit) so the release runs with the fixed workflow.Also note the earlier v0.21.0 attempt already created the GitHub release + git tag; that may need cleaning up before re-running so GoReleaser doesn't trip on an existing release.
Testing
Can't exercise the publish path without pushing a tag. Fix is based on npm/cli#9722 (npm 12 sigstore regression) and the documented Node 24 LTS trusted-publishing baseline.