fix(ci): restore registry-url in release trusted-publish workflow#11
Merged
stevenobiajulu merged 1 commit intomainfrom Feb 25, 2026
Merged
fix(ci): restore registry-url in release trusted-publish workflow#11stevenobiajulu merged 1 commit intomainfrom
stevenobiajulu merged 1 commit intomainfrom
Conversation
Even with Node 22 and id-token permissions, npm publish was failing in release with ENEEDAUTH, meaning trusted publishing was not being engaged.\n\nsetup-node's registry-url configuration is part of npm's recommended trusted publishing setup. This restores registry-url in all release jobs while keeping token cleanup to avoid stale token fallback.\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: restore registry-url in setup-node for all release jobs. Why: release publish still fails with ENEEDAUTH, indicating trusted publishing is not being engaged; this aligns with npm's documented setup while keeping token cleanup and Node 22. Ref: #9.