Skip to content

docs: the registry-side trusted publisher is owner work, not a given #5

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

Merged
firejune merged 1 commit into from
Aug 23, 2026
Merged

docs: the registry-side trusted publisher is owner work, not a given #5

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
6 changes: 4 additions & 2 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,8 +108,10 @@ releases.

### The registry side (owner, npmjs.com)

**Configured — recorded here for when it needs to change.** The form needs
the package owner's npm account, once per package:
**Owner-side, and the one step this automation can neither do nor verify.**
The form needs the package owner's npm account, once per package — and until
it matches, every automated publish fails with `ENEEDAUTH` (npm finds no
trusted publisher willing to exchange its OIDC token):

npmjs.com → *package* → **Settings** → **Trusted Publisher** → *GitHub
Actions*, filled in identically for **`byteguard`** and
Expand Down
Loading