docs: clarify trusted publishing Node/npm versions... (#1869)
David D'Alessandro committed
Feb 9, 2026 at 15:05 UTC
e19aaacfc0f5991c75c8508483e75ac041a1fe4a
1 file changed
+2
-2
content/packages-and-modules/securing-your-code/trusted-publishers.mdx
+2
-2
@@ -6,7 +6,7 @@ Trusted publishing allows you to publish npm packages directly from your CI/CD w
6
7
<Note>
8
9
-**Note:** Trusted publishing requires [npm CLI](https://docs.npmjs.com/cli/v11) version 11.5.1 or later.
9
+**Note:** Trusted publishing requires [npm CLI](https://docs.npmjs.com/cli/v11) version 11.5.1 or later and Node version 22.14.0 or higher.
10
11
</Note>
12
@@ -141,7 +141,7 @@ The `id_tokens` configuration tells GitLab to generate an OIDC token for npm. Le
141
142
### Managing trusted publisher configurations
143
144
-You can modify or remove your trusted publisher configuration at any time through your package settings on [npmjs.com](https://npmjs.com). Each package can only have one trusted publisher connection at a time, but this connection can be edited or deleted as needed. To change providers (for example, switching from GitHub Actions to GitLab CI/CD), simply edit your existing configuration and select the new provider. The change takes effect immediately for future publishes. To remove trusted publishing entirely and return to token-based authentication, delete the trusted publisher configuration from your package settings.
144
+You can modify or remove your trusted publisher configuration at any time through your package settings on [npmjs.com](https://npmjs.com) → Packages → YOUR_PACKAGE → Settings → Trusted publishing. Each package can only have one trusted publisher connection at a time, but this connection can be edited or deleted as needed. To change providers (for example, switching from GitHub Actions to GitLab CI/CD), simply edit your existing configuration and select the new provider. The change takes effect immediately for future publishes. To remove trusted publishing entirely and return to token-based authentication, delete the trusted publisher configuration from your package settings.
145
146
## Recommended: Restrict token access when using trusted publishers
147