docs: gate release merges and tagging on polled CI success - #255
Merged
Conversation
Also pin the publish job to npm 11 so trusted publishing works on Node 22.22.1.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This was referenced Aug 18, 2026
Merged
Merged
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.
Summary
npm@^11so trusted publishing works on Node 22.22.1Background
The v0.0.17 publish run failed at
npm install -g npm@latest: npm 12 requires Node^22.22.2 || ^24.15.0 || >=26.0.0, but the workflow runs Node 22.22.1. npm 11.18.0 satisfies both that Node range and the npm >= 11.5.1 requirement for OIDC trusted publishing.Verification
npm view npm@latest engines->node: ^22.22.2 || ^24.15.0 || >=26.0.0npm view npm@11 engines->node: ^20.17.0 || >=22.9.0