Skip to content

Avoid repeated npm login for OIDC releases #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
raghubetina wants to merge 1 commit into from
Closed

Avoid repeated npm login for OIDC releases #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,3 +11,7 @@ in `docs/release-history.md`. When behavior changes, update its owning document
is complete only after that exact candidate passes its explicitly named release-specific qualification, is
separately approved, and is selected by npm's `latest` dist-tag. Preserve dated alpha observations as history
rather than describing them as current channel state.
- The authenticated npm access and trust checks in `RELEASING.md` are configuration audits. For an ordinary release,
verify the retained GitHub workflow/environment binding and protected tag; do not require another npm login or
`npm trust list`/2FA ceremony unless that configuration changed. OIDC publication confirms the retained binding.
Moving an existing version's `latest` dist-tag still requires ordinary npm authentication.