Add original error code for search (#1919)
Very small change. I wasted several days before finding this documentation; the npm output never shows "Unable to authenticate" but "ENEEDAUTH"
初绎 committed
Mar 21, 2026 at 00:03 UTC
47f28899faa6fffae9b971dad6918fb8b72074d7
1 file changed
+1
-1
content/packages-and-modules/securing-your-code/trusted-publishers.mdx
+1
-1
@@ -324,7 +324,7 @@ Consider implementing these additional security practices:
324
325
## Troubleshooting
326
327
-If you encounter an "Unable to authenticate" error when publishing, first verify that the workflow filename matches exactly what you configured on [npmjs.com](https://npmjs.com), including the `.yml` extension. All fields are case-sensitive and must be exact. Also ensure you're using GitHub-hosted runners, GitLab.com shared runners, or CircleCI cloud, as self-hosted runners are not currently supported. For GitHub Actions specifically, check that the `id-token: write` permission is set in your workflow. For CircleCI, verify that your Organization ID, Project ID, and Pipeline definition ID match your CircleCI configuration.
327
+If you encounter an "Unable to authenticate" (ENEEDAUTH) error when publishing, first verify that the workflow filename matches exactly what you configured on [npmjs.com](https://npmjs.com), including the `.yml` extension. All fields are case-sensitive and must be exact. Also ensure you're using GitHub-hosted runners, GitLab.com shared runners, or CircleCI cloud, as self-hosted runners are not currently supported. For GitHub Actions specifically, check that the `id-token: write` permission is set in your workflow. For CircleCI, verify that your Organization ID, Project ID, and Pipeline definition ID match your CircleCI configuration.
328
329
<Note>
330