Validate NPM token before creating a release#56501
Closed
cipolleschi wants to merge 1 commit into
Closed
Conversation
Summary: Add an early NPM token validation step to the create-release workflow. This runs `npm whoami` right after checkout to fail fast if the token is expired or invalid, avoiding wasted CI time on a release that would fail at the publish step. The step gracefully skips when no token is present (e.g. fork PRs). Reviewed By: christophpurrer Differential Revision: D101377190
meta-cla
Bot
added
the
CLA Signed
|
@cipolleschi has exported this pull request. If you are a Meta employee, you can view the originating Diff in D101377190. |
Collaborator
|
This pull request was successfully merged by @cipolleschi in 0223364 When will my fix make it into a release? | How to file a pick request? |
|
This pull request has been merged in 0223364. |
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
2 participants
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.
Summary:
Add an early NPM token validation step to the create-release workflow.
This runs
npm whoamiright after checkout to fail fast if the token isexpired or invalid, avoiding wasted CI time on a release that would fail
at the publish step.
The step gracefully skips when no token is present (e.g. fork PRs).
Reviewed By: christophpurrer
Differential Revision: D101377190
Changelog:
[Internal] -