fix(ci): run release workflow on Node 22 for trusted publishing#10
Merged
stevenobiajulu merged 1 commit intomainfrom Feb 25, 2026
Merged
Conversation
Trusted publishing with npm now requires a Node 22.14+ runtime. The release jobs were running on Node 20, so npm did not enter OIDC trusted-publishing mode and failed with ENEEDAUTH (interactive auth required).\n\nThis updates all release workflow jobs to Node 22 so the publish step can use OIDC provenance instead of manual npm login.\n\nRef: #9
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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: switch release workflow jobs from Node 20 to Node 22. Why: npm trusted publishing requires Node 22.14+; Node 20 caused publish to fail with ENEEDAUTH instead of using OIDC. Ref: #9.