Skip to content

Commit 80b0e3e

Browse files
committed
[docs] Add 2FA requirements for publishing unscoped public packages
1 parent 357dbec commit 80b0e3e

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

content/packages-and-modules/contributing-packages-to-the-registry/creating-and-publishing-unscoped-public-packages.mdx

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -58,6 +58,16 @@ npm install path/to/my-package
5858

5959
## Publishing unscoped public packages
6060

61+
<Note>
62+
63+
**Important:** Before you can publish, you must have either:
64+
- [Two-factor authentication (2FA)][config-2fa] enabled on your account, OR
65+
- A [granular access token with bypass 2FA enabled][creating-token] (required for CI/CD workflows)
66+
67+
For more information, see "[Requiring 2FA for package publishing][requiring-2fa]."
68+
69+
</Note>
70+
6171
1. On the command line, navigate to the root directory of your package.
6272

6373
```
@@ -89,3 +99,6 @@ For more information on the `publish` command, see the [CLI documentation][cli-p
8999
[cli-publish]: /cli/publish
90100
[pii]: https://en.wikipedia.org/wiki/Personally_identifiable_information
91101
[provenance-how-to]: /generating-provenance-statements
102+
[config-2fa]: /configuring-two-factor-authentication
103+
[creating-token]: /creating-and-viewing-access-tokens
104+
[requiring-2fa]: /requiring-2fa-for-package-publishing-and-settings-modification

0 commit comments

Comments
 (0)