ci: drop the stage list call that cannot authenticate in CI - #7
Merged
Merged
Conversation
Listing staged packages needs a user token; under OIDC it returns E401 and only adds a red line to every release. npm stage publish already prints the stage id.
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.
Listing staged packages needs a user token; under OIDC it returns E401 and only adds a red line to every release.
npm stage publishalready prints the stage id, so the summary now says where to find it and why the workflow cannot list it itself.The v0.1.2 release staged successfully with this workflow (stage id
45ab2a50-ab3a-4e54-b9cf-4287214cdf04, provenance logged to Sigstore), so this only removes noise from the next one.