Repository navigation
ci: publish @sanring/cli with npm trusted publishing - #47
Merged
Merged
Conversation
Token publish keeps asking for OTP. GitHub Actions can publish @sanring/cli with id-token instead of NPM_TOKEN. Co-authored-by: Cursor <cursoragent@cursor.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_TOKEN. Token publish is hitting EOTP even with Bypass 2FA checked.id-token: writeso npm can authenticate with GitHub OIDC..npmrcso changesets/action does not write the token file that forces OTP.After this lands, add a Trusted Publisher on
@sanring/cli(see PR comment / chat) and re-run Release. It will publish 0.27.0.Test plan
sanringtech/ui/release.ymlnpm publish@sanring/cli@0.27.0Made with Cursor