[update]: legacy access token creation workflow from access tokens documentation
#1756
+17
−66
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
jpg619
commented
Oct 27, 2025
jpg619
commented
Oct 27, 2025
jpg619
commented
Oct 27, 2025
jpg619
commented
Oct 27, 2025
...t/integrations/integrating-npm-with-external-services/creating-and-viewing-access-tokens.mdx
Show resolved
Hide resolved
jpg619
commented
Oct 27, 2025
jpg619
commented
Oct 27, 2025
|
Only the last two files changed in this PR are actually sourced from this repo. The rest are legacy docs for old versions of npm, sourced from https://github.com/npm/cli itself. We don't need to backport updates there, only the latest version of docs for registry-specific things are authoritative. We may want to consider adding warning headers when folks are browsing legacy docs to remind them, but that's outside the scope of this PR. |
|
Additionally, those proposed changes would be incorrect for those old version of npm. The defaults are baked into npm itself, not the registry. Those files are build directly from npm config itself. We intentionally made a tight coupling there so that docs would reflect reality. Changing those defaults would have to wait till npm 12. |
jpg619
commented
Oct 30, 2025
...ations/integrating-npm-with-external-services/using-private-packages-in-a-ci-cd-workflow.mdx
Outdated
Show resolved
Hide resolved
jpg619
commented
Oct 30, 2025
| - **token:** The first digits of the actual token. | ||
| - **create:** Date the token was created. | ||
| - **readonly:** If yes, indicates a read-only token. If no, indicates a token with both read and publish permissions. | ||
| - **created:** Date the token was created. |
jpg619
commented
Oct 30, 2025
|
|
||
| - [Legacy tokens](#about-legacy-tokens) | ||
| - [Granular access tokens](#about-granular-access-tokens) | ||
| As of November 2025, access tokens can only be [Granular access tokens](#about-granular-access-tokens). Legacy access tokens are deprecated. |
jpg619
commented
Oct 30, 2025
| For more information on creating and viewing access tokens on the web and CLI, see "[Creating and viewing access tokens][create-token]". | ||
|
|
||
| ## About legacy tokens | ||
| ## About legacy tokens (Deprecated) |
…ion as deprecated
jpg619
commented
Oct 30, 2025
...ations/integrating-npm-with-external-services/using-private-packages-in-a-ci-cd-workflow.mdx
Outdated
Show resolved
Hide resolved
dhei
reviewed
Oct 30, 2025
content/integrations/integrating-npm-with-external-services/about-access-tokens.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Di Hei <dhei@github.com>
Added a warning about the deprecation of legacy access tokens.
jpg619
commented
Oct 30, 2025
|
|
||
| If you use a legacy token instead, by default, `npm token create` will generate a token with both read and write permissions. We recommend creating a read-only token: | ||
|
|
||
| <Note variant="danger"> |
dhei
reviewed
Oct 30, 2025
content/integrations/integrating-npm-with-external-services/about-access-tokens.mdx
Outdated
Show resolved
Hide resolved
dhei
reviewed
Oct 30, 2025
content/integrations/integrating-npm-with-external-services/about-access-tokens.mdx
Outdated
Show resolved
Hide resolved
dhei
reviewed
Oct 30, 2025
...ations/integrating-npm-with-external-services/using-private-packages-in-a-ci-cd-workflow.mdx
Outdated
Show resolved
Hide resolved
…out-access-tokens.mdx Co-authored-by: Di Hei <dhei@github.com>
…ing-private-packages-in-a-ci-cd-workflow.mdx Co-authored-by: Di Hei <dhei@github.com>
…out-access-tokens.mdx Co-authored-by: Di Hei <dhei@github.com>
jpg619
commented
Oct 30, 2025
|
|
||
| - [Legacy tokens](#about-legacy-tokens) | ||
| - [Granular access tokens](#about-granular-access-tokens) | ||
| As of November 2025, access tokens can only be [Granular access tokens](#about-granular-access-tokens). Legacy access tokens are removed. |
…D workflow documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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: Added notes on deprecated legacy access token references and removed few documentation due to deprecation
File Changes (3 files)
content/integrations/integrating-npm-with-external-services/creating-and-viewing-access-tokens.mdxcontent/integrations/integrating-npm-with-external-services/about-access-tokens.mdxcontent/integrations/integrating-npm-with-external-services/using-private-packages-in-a-ci-cd-workflow.mdxChanges Made
notefor legacy token creation workflow from access tokens documentation