chore(release): 0.10.1 — fix the npm publish leg - #207
Merged
Conversation
publish-npm died on 'npm install -g npm@latest': latest is now npm 12, which requires node >=22 while the job pinned node 20. Node bumped to 24 and npm major-pinned to 11 (trusted publishing needs >=11.5.1) so the step stops chasing a moving target. v0.10.0 shipped binaries and crates but never reached npm; this patch cut delivers it.
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.
v0.10.0's publish-npm leg failed on
npm install -g npm@latest(npm 12 requires node ≥22; the job pins node 20). All five platform builds and the crates.io publish succeeded, and the release-notes fix verified (exactly one What's Changed). This cut: node 24 + major-pinned npm@11 in the workflow, version bumped to 0.10.1 so npm gets a clean publish. npm jumps 0.9.0 → 0.10.1.🤖 Generated with Claude Code