Repository navigation
chore: npm Trusted Publishing + 0.7.1 republish - #29
Merged
Merged
Conversation
publish.yml drops NODE_AUTH_TOKEN so npm publish authenticates with the OIDC token (id-token: write was already granted). A token in the env would take precedence over OIDC. 0.7.1 is a docs-only republish whose job is to validate the new trusted publisher connection.
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
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.
Switches
publish.ymlfromNPM_TOKENto npm Trusted Publishing (OIDC). The trusted publisherdevslab-kr/numkey · publish.ymlis registered on npm and is pending validation until one publish succeeds before 2026-11-10 15:03 UTC — 0.7.1 (docs-only republish) is that publish.Local
npm run verifygreen. After merge:gh workflow run publish.yml -f version=v0.7.1./ npm 발행을 토큰에서 Trusted Publishing(OIDC)으로 전환. 0.7.1은 연결 검증용 재배포.