Prepare gated release-level OIDC publication - #189
Merged
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
douglas-grishen
marked this pull request as ready for review
September 22, 2026 01:53
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
2 participants
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.
Staged approval of the coordinated release required repeated passkey prompts and then fell back to an unavailable OTP. This prepares a separate, disabled-by-default release-level OIDC flow so the owner can authorize one exact cohort in GitHub instead of approving each package in npm.
The new workflow retains unprivileged audit/build/test/pack/consumer preparation, gates publication through
npm-release, and publishes only verified tarballs with short-lived OIDC credentials. It checks every archive before the first write, orders dependencies through the existing release helper, stops on failure, and resumes only when existing registry bytes, ECDSA signatures, tags and source/workflow provenance match. Read-only registry consumers remain mandatory after publication. Legacy staging remains available.Activation is NOT included: no npm trust settings, GitHub environments, enablement flags or package versions have been changed. The migration document spells out the publication authority change and recommends a fresh version because beta.9 is already partially public/staged. Initial npm publisher configuration still requires maintainer authorization.
Validation: 48 focused release/policy tests passed, including mutated artifacts, forbidden hooks, symlinks, actor/workflow/branch substitutions, dependency failures, exact resume and signature/provenance/tag mismatches. Public-surface audit and YAML parsing passed. The signature and downloaded-byte verifier also passed read-only checks against the three already-public beta.9 packages. Live direct OIDC publication cannot be validated until the separate activation is authorized.