Repository navigation
release: verify tokenless publishing with RC2 - #5
Merged
Merged
Conversation
Prepare coordinated 0.1.0-rc.2 packages without API changes and remove the release helper's obsolete branch-token workflow gate. Retain CI, upstream, package, tag, and owning-branch validation; add a regression test for the OIDC release path.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Problem and outcome
Complete the user-requested end-to-end verification of npm trusted publishing with coordinated 0.1.0-rc.2 artifacts. No package API changes.
Delivery context
Single-repository follow-up to merged #4 (6f64319). No cross-repository dependencies. All three npm trusted publishers are configured for this repository, publish.yml, and Publish environment, allowing direct publication.
Implementation and validation
Landing and verification
User explicitly requested completing verification after #4 merged. Land this exact single-PR cut after CI, then publish tag v0.1.0-rc.2 through the existing OIDC-only workflow. Verify all three registry versions/gitHeads/provenance and a successful workflow. Retire the obsolete GitHub secret and disallow bypass-token publishing after success. No full cross-repository E2E needed for release metadata/helper-only changes. Existing RC1 artifacts and tag remain unchanged.
Verified release evidence
6956f94a8f7d6ab5e144124db7fdab018cbd8f4f._npmUserisGitHub Actions <npm-oidc-no-reply@github.com>; each exposes SLSA provenance.npm audit signaturesverified 259 registry signatures and 50 attestations across the installed dependency tree.