Repository navigation
docs(release): name the Allowed-actions trap in the trusted-publisher notes - #2
Merged
Merged
Conversation
… notes The header lists the four fields a trusted publisher needs, and a release run configured exactly that way still failed with `403 OIDC permission denied for this action` after the provenance was signed. The fifth field, "Allowed actions", defaults to `npm stage publish` only for configurations created after 2026-09-03, and this workflow runs `npm publish`. Older configurations (before 2026-05-20) got `npm publish` automatically, which is why the same file publishes one package and not another. The comment now names the field, the default, and the symptom. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Comment-only change to the trusted-publisher notes in
release.yml.Why: nextup v0.1.2 and v0.1.3 release runs failed with
403 OIDC permission denied for this actionafter the provenance statement was signed, with a trusted-publisher configuration that matched every field the header lists. The missing piece is npm's "Allowed actions" field: configurations created after 2026-09-03 default tonpm stage publishonly, while this workflow runsnpm publish. Configurations created before 2026-05-20 gotnpm publishautomatically, which is why the identical file publishes@hansenexus/mechanicsand not@hansenexus/nextup.What: the header now lists
Allowed actions: npm publish (ticked)next to the other four fields and describes the default and the symptom, so the next package set up from this template does not hit it.No workflow logic changes. Source: npm docs, Trusted publishing for npm packages.
🤖 Generated with Claude Code