Add support for --no-2fa flag
#559
Merged
Conversation
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
papb
suggested changes
Jul 29, 2020
Co-authored-by: Sindre Sorhus <[email protected]>
Co-authored-by: Pedro Augusto de Paula Barbosa <[email protected]>
This was referenced Mar 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This adds a
--no-2faCLI option as discussed in #398 to bypass enabling 2FA on new packages.The check is pretty trivial; if the 2Fa option is set to false, the task is skipped. Default value is true.
One of the reasons I'm wanting this is that I use
semantic-releaseto handle releasing my packages, which requires not having 2fa enabled. I'm looking to usenpfor doing some pre-publishing of an upcoming package of mine, assemantic-releasedoes not support0.x.xversions.Fixes #398
Closes #515 (by superseding)