fix(ci): use Publish environment for all release types#1138
Merged
Conversation
npm trusted publishing OIDC tokens must be issued for the same environment configured on npmjs.com. Dry-run was using no environment, causing the OIDC check to fail. Co-Authored-By: Claude Opus 4.6 <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.
Summary
npm trusted publishing OIDC tokens include the GitHub environment name. Since all 17 packages were configured on npmjs.com with environment
Publish, the dry-run was failing because it ran without an environment — the OIDC token didn't match.Changed from conditional environment to always using
Publishfor all release types (dry-run, beta, production).Test plan
🤖 Generated with Claude Code