馃敀 add provenance release workflow - #23
Merged
Merged
Conversation
Validate one exact tarball before isolating npm OIDC and GitHub Release permissions. Bootstrap only rc.0 with a temporary token, then stage later releases for npm 2FA approval before announcing them.
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.
Summary
release.ymlwith isolated validation, npm, and GitHub Release permissions1.0.0-rc.0with a temporary token and stage later versions through OIDC for npm 2FA approvallatestabsenceVerification
npm run format:checknpm run lintnpm run typechecknpm run test:typesnpm test(75 tests)npm run test:consumernpm run package:checkplus preserved-tarball inspection and SHA-512 transfer checkCI=1 npm run test:browser:container(23 tests)npm run security:audit(root and packed consumer: 0 vulnerabilities)release.ymlparsed with Ruby YAMLThe combined local
release:checkreached the browser suite, where the existing Ctrl-click popup test flaked once under the local 8-worker mode; the release-equivalent single-worker CI rerun passed all 23 tests. Hosted CI remains the authoritative browser result for this PR.After merge
No tag should be created yet. The
npm-publishenvironment and temporary bootstrap secret must be configured beforev1.0.0-rc.0; npm trusted publishing is configured only after that first package version exists.