ci: fix OIDC trusted publishing (drop registry-url) - #8
Merged
Conversation
setup-node's registry-url writes an .npmrc auth-token placeholder that npm sends instead of doing the OIDC exchange, which the registry rejects as a 404. Drop it, allow manual dispatch with a tag to re-publish a release whose automatic run failed, and normalize repository.url. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The v0.1.1 publish failed with
404 Not Found - PUT …: npm masks auth failures on scoped packages as 404s. Cause:setup-node'sregistry-urloption writes an.npmrcwith an auth-token placeholder (NODE_AUTH_TOKEN=XXXXX-…), and npm sends that bogus token instead of attempting the OIDC trusted-publishing exchange. Thealways-authwarning in the log is the same.npmrctalking.registry-urlfromsetup-node— trusted publishing needs no registry auth config at allworkflow_dispatchtrigger with ataginput (checks out and stamps that tag) so a release whose automatic publish failed can be re-published without deleting/recreating the GitHub release — needed right now forv0.1.1repository.urlwithgit+to silence npm's normalization warning at publishAfter merging: dispatch the workflow with
tag: v0.1.1. Requires the trusted publisher on npm to be registered as repoangular-gsap/core, workflowrelease.yml.🤖 Generated with Claude Code