Add a loglevel input to the publish workflow#8
Merged
Conversation
Two 3.0.0 publish attempts have now failed with `E403 Forbidden - PUT` at the very last step, and npm's default `notice` output says nothing at all about the OIDC exchange — there is no way to tell from the log whether npm attempted it, or what the registry objected to. Expose the npm loglevel as a workflow_dispatch choice so a publish can be re-run with `verbose` (or `silly`) without editing this file under time pressure. `release` events pass no inputs, hence the `|| 'notice'` fallback, and the value goes through `env:` rather than being interpolated into the script body. Co-Authored-By: Claude Opus 5 (1M context) <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.
Two 3.0.0 publish attempts have now failed with
E403 Forbidden - PUT https://registry.npmjs.org/simple-builderat the very last step, after all five gates pass. npm's defaultnoticeoutput says nothing about the OIDC exchange — there's no way to tell from the log whether npm attempted it, or what the registry objected to. Both prior hypotheses (theNODE_AUTH_TOKENenv, then the_authTokenlineregistry-urlwrites) are now ruled out: the guard step confirms no credential is configured and the 403 is unchanged.Exposes the npm loglevel as a
workflow_dispatchchoice (notice/verbose/silly) so a publish can be re-run with verbose output without editing this file under time pressure — and so future releases stay debuggable.releaseevents pass no inputs, hence the|| 'notice'fallback. The value goes throughenv:rather than being interpolated into the script body, matching the existing tag guard's handling.No source or test changes.
🤖 Generated with Claude Code