fix(ci): provenance를 NPM_CONFIG_PROVENANCE env로 켜기#31
Merged
Conversation
zpl-core@0.1.1 발행 시 --provenance 플래그를 줬으나 attestations가 0개였다. pnpm 10.x는 publish를 npm CLI로 위임하는데 이 경로에서 --provenance 플래그가 no-op이다. env NPM_CONFIG_PROVENANCE=true가 실제 트리거이므로 두 publish 워크플로에 추가한다. 다음 발행(0.1.2·react-zpl)부터 provenance가 첨부된다. 이미 나간 0.1.1은 재발행 불가라 그대로 둔다. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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.
zpl-core@0.1.1발행 시--provenance플래그를 줬으나 attestations가 0개였습니다. pnpm 10.x는 publish를 npm CLI로 위임하는데 그 경로에서--provenance플래그가 no-op입니다.NPM_CONFIG_PROVENANCE=trueenv가 실제 트리거라 두 publish 워크플로에 추가합니다.다음 발행(0.1.2·react-zpl)부터 provenance가 첨부됩니다. 이미 나간 0.1.1은 재발행 불가라 그대로 둡니다.