Repository navigation
fix(release): add scoped temporary npm credential fallback - #9
Merged
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.
npm rejects immutable GitHub OIDC subjects before publishing despite valid trusted-publisher configuration. Allow a temporary
NPM_RELEASE_TOKENin the Production environment to authenticate SDK and CLI publication while retaining provenance and every existing quality/native gate.The secret is passed only to authentication and publication steps. Verification/native build jobs never receive it. Removing the environment secret restores OIDC. The SDK recovery may use a new flat recovery tag, compatible with Production's existing tag policy, while publishing the original immutable SDK revision. Anonymous SDK availability and provenance are verified after publication, so staged versions do not count as released.
The recovery runbook documents one-day expiration, eleven explicit package permissions, no organization administration rights, private secret setup, and credential cleanup.
Validation: 40 release-boundary tests passed, including credential isolation and rejection of unrelated recovery refs; lint, formatting, YAML/shell syntax, and git diff checks passed.