Avoid repeated npm login for OIDC releases - #32
Closed
raghubetina wants to merge 1 commit into
Closed
raghubetina wants to merge 1 commit into
raghubetina wants to merge 1 commit into
Conversation
Treat authenticated access and trust checks as configuration audits. Routine releases verify the retained workflow binding and protected tag, while an existing-version dist-tag move still needs npm auth.
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
1 participant
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.
Routine GitHub OIDC releases were repeatedly requesting interactive npm authentication for administrative trust/access checks. Clarify the standing operating policy in the agent instructions: verify the retained workflow/environment binding and protected tag; request interactive configuration checks when that configuration changes.
Moving an existing version to
lateststill requires npm authentication. This changes no package or runtime bytes and does not publish a new version.Validation: full
npm run checkpassed, including type checking, lint, formatting, tests, package allowlist, and packed-package smoke.