Use staged npm publishing for language releases - #7
Merged
Conversation
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.
背景
Language package releases should use the same human-approved npm supply-chain boundary as the engine package. The first release remains a one-time authenticated bootstrap because npm requires an existing package before Trusted Publisher configuration.
実装方法
npm stage publishlanguage-v<version>tag, ancestry, tests, types, package audit, registry, and provenance gatesテスト方法
npm cinpm run test:languagenpm run typecheck:languagenpm run pack:checknpm audit --audit-level=highReview 視点 / 懸念点
npm stage publishfor workflowrelease-language.yaml.0.1.0package is published manually before this trust relationship can be configured.