Skip to content

docs(release): name the Allowed-actions trap in the trusted-publisher notes #2

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
Lenoux01 merged 1 commit into from
Sep 9, 2026
Merged

docs(release): name the Allowed-actions trap in the trusted-publisher notes #2

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
9 changes: 9 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,15 @@ name: release
# Repository nextup
# Workflow filename release.yml
# Environment (blank)
# Allowed actions npm publish (ticked)
#
# "Allowed actions" is the trap. A configuration created after 2026-09-03
# defaults to `npm stage publish` only, and this workflow runs `npm publish`.
# The symptom is a run that signs the provenance and then dies with
# `403 OIDC permission denied for this action`: the token exchange succeeded,
# the action was refused. Configurations created before 2026-05-20 got
# `npm publish` automatically, which is why an older package's copy of this
# file publishes while a new package's does not (nextup v0.1.2/v0.1.3, 2026-09-08).
#
# Renaming this file, or moving the job to another workflow, breaks publishing
# until that field is updated to match.
Expand Down
Loading