ci: authenticate the first publish with the token, after all - #5
Closed
catomean wants to merge 1 commit into
Closed
Conversation
The OIDC change one PR ago was the right destination in the wrong order: a trusted publisher is configured on a PACKAGE, and this package does not exist yet. With the token wiring gone and OIDC not yet possible, a tag push would have failed to authenticate by either route. The bootstrap release therefore uses NPM_TOKEN (now set on this repo). Once the package exists, the trusted publisher is configured, this env block goes away again, and the token is revoked. Provenance is unaffected — `id-token: write` is what npm needs to attest the build, independent of how the publish authenticates. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Collaborator
Author
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 OIDC change one PR ago (#3) was the right destination reached in the wrong order: a trusted publisher is configured on a package, and this package doesn't exist yet. With the token wiring gone and OIDC not yet possible, a tag push would have failed to authenticate by either route.
The bootstrap release therefore uses
NPM_TOKEN, now set on this repo. Ordering that works:publish.ymlenvblock againProvenance is unaffected —
id-token: writeis what npm needs to attest the build, independent of how the publish authenticates.Mirrors ai-forms#14 so both libraries stay identical.
🤖 Generated with Claude Code