Skip to content

Handle npm tokens with environment variables #1940

Handle npm tokens with environment variables

Handle npm tokens with environment variables #1940

Triggered via pull request April 21, 2026 23:41
Status Failure
Total duration 1m 36s
Artifacts

pr.yml

on: pull_request
build docs
20s
build docs
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 2 warnings
build (ubuntu-latest, node 20, npm 11)
Process completed with exit code 1.
packagePublish › with real local registry › errors and does not retry on republish: packages/beachball/src/__functional__/packageManager/packagePublish.test.ts#L169
expect(received).toEqual(expected) // deep equality - Expected - 2 + Received + 31 - ObjectContaining { - "success": true, + Object { + "all": "npm warn Unknown env config \"version-commit-hooks\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-tag-prefix\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-git-message\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"argv\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-git-tag\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm error code ENEEDAUTH + npm error need auth This command requires you to be logged in to http://localhost:4873/ + npm error need auth You need to authorize this machine using `npm adduser` + npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-04-21T23_42_21_022Z-debug-0.log", + "command": "npm publish --registry http://localhost:4873 --tag testbeachballtag --loglevel warn", + "escapedCommand": "npm publish --registry \"http://localhost:4873\" --tag testbeachballtag --loglevel warn", + "exitCode": 1, + "failed": true, + "isCanceled": false, + "killed": false, + "shortMessage": "Command failed with exit code 1: npm publish --registry http://localhost:4873 --tag testbeachballtag --loglevel warn", + "signal": undefined, + "signalDescription": undefined, + "stderr": "npm warn Unknown env config \"version-commit-hooks\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-tag-prefix\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-git-message\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"argv\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-git-tag\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm error code ENEEDAUTH + npm error need auth This command requires you to be logged in to http://localhost:4873/ + npm error need auth You need to authorize this machine using `npm adduser` + npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-04-21T23_42_21_022Z-debug-0.log", + "stdout": "", + "success": false, + "timedOut": false, } at Object.<anonymous> (src/__functional__/packageManager/packagePublish.test.ts:169:29)
packagePublish › with real local registry › can publish with a token: packages/beachball/src/__functional__/packageManager/packagePublish.test.ts#L121
expect(received).toEqual(expected) // deep equality - Expected - 2 + Received + 31 - ObjectContaining { - "success": true, + Object { + "all": "npm warn Unknown env config \"version-commit-hooks\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-tag-prefix\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-git-message\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"argv\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-git-tag\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm error code ENEEDAUTH + npm error need auth This command requires you to be logged in to http://localhost:4873/ + npm error need auth You need to authorize this machine using `npm adduser` + npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-04-21T23_42_18_528Z-debug-0.log", + "command": "npm publish --registry http://localhost:4873 --tag testbeachballtag --loglevel warn", + "escapedCommand": "npm publish --registry \"http://localhost:4873\" --tag testbeachballtag --loglevel warn", + "exitCode": 1, + "failed": true, + "isCanceled": false, + "killed": false, + "shortMessage": "Command failed with exit code 1: npm publish --registry http://localhost:4873 --tag testbeachballtag --loglevel warn", + "signal": undefined, + "signalDescription": undefined, + "stderr": "npm warn Unknown env config \"version-commit-hooks\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-tag-prefix\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-git-message\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"argv\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm warn Unknown env config \"version-git-tag\". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options. + npm error code ENEEDAUTH + npm error need auth This command requires you to be logged in to http://localhost:4873/ + npm error need auth You need to authorize this machine using `npm adduser` + npm error A complete log of this run can be found in: /home/runner/.npm/_logs/2026-04-21T23_42_18_528Z-debug-0.log", + "stdout": "", + "success": false, + "timedOut": false, } at Object.<anonymous> (src/__functional__/packageManager/packagePublish.test.ts:121:29)
build (windows-latest, node 14, npm 8)
The strategy configuration was canceled because "build.ubuntu-latest_11_20" failed
build (windows-latest, node 14, npm 8)
The operation was canceled.
build (windows-latest, node 20, npm 11)
The strategy configuration was canceled because "build.ubuntu-latest_11_20" failed
build (windows-latest, node 20, npm 11)
The operation was canceled.
build (ubuntu-latest, node 14, npm 8)
The strategy configuration was canceled because "build.ubuntu-latest_11_20" failed
build (ubuntu-latest, node 14, npm 8)
The operation was canceled.
packagePublish › with real local registry › errors and does not retry on republish: packages/beachball/src/__functional__/packageManager/packagePublish.test.ts#L169
expect(received).toEqual(expected) // deep equality - Expected - 2 + Received + 25 - ObjectContaining { - "success": true, + Object { + "all": "npm ERR! code ENEEDAUTH + npm ERR! need auth This command requires you to be logged in to http://localhost:4873/ + npm ERR! need auth You need to authorize this machine using `npm adduser` + + npm ERR! A complete log of this run can be found in: + npm ERR! /home/runner/.npm/_logs/2026-04-21T23_42_36_261Z-debug-0.log", + "command": "npm publish --registry http://localhost:4873 --tag testbeachballtag --loglevel warn", + "escapedCommand": "npm publish --registry \"http://localhost:4873\" --tag testbeachballtag --loglevel warn", + "exitCode": 1, + "failed": true, + "isCanceled": false, + "killed": false, + "shortMessage": "Command failed with exit code 1: npm publish --registry http://localhost:4873 --tag testbeachballtag --loglevel warn", + "signal": undefined, + "signalDescription": undefined, + "stderr": "npm ERR! code ENEEDAUTH + npm ERR! need auth This command requires you to be logged in to http://localhost:4873/ + npm ERR! need auth You need to authorize this machine using `npm adduser` + + npm ERR! A complete log of this run can be found in: + npm ERR! /home/runner/.npm/_logs/2026-04-21T23_42_36_261Z-debug-0.log", + "stdout": "", + "success": false, + "timedOut": false, } at Object.<anonymous> (src/__functional__/packageManager/packagePublish.test.ts:169:29)
packagePublish › with real local registry › can publish with a token: packages/beachball/src/__functional__/packageManager/packagePublish.test.ts#L121
expect(received).toEqual(expected) // deep equality - Expected - 2 + Received + 25 - ObjectContaining { - "success": true, + Object { + "all": "npm ERR! code ENEEDAUTH + npm ERR! need auth This command requires you to be logged in to http://localhost:4873/ + npm ERR! need auth You need to authorize this machine using `npm adduser` + + npm ERR! A complete log of this run can be found in: + npm ERR! /home/runner/.npm/_logs/2026-04-21T23_42_33_548Z-debug-0.log", + "command": "npm publish --registry http://localhost:4873 --tag testbeachballtag --loglevel warn", + "escapedCommand": "npm publish --registry \"http://localhost:4873\" --tag testbeachballtag --loglevel warn", + "exitCode": 1, + "failed": true, + "isCanceled": false, + "killed": false, + "shortMessage": "Command failed with exit code 1: npm publish --registry http://localhost:4873 --tag testbeachballtag --loglevel warn", + "signal": undefined, + "signalDescription": undefined, + "stderr": "npm ERR! code ENEEDAUTH + npm ERR! need auth This command requires you to be logged in to http://localhost:4873/ + npm ERR! need auth You need to authorize this machine using `npm adduser` + + npm ERR! A complete log of this run can be found in: + npm ERR! /home/runner/.npm/_logs/2026-04-21T23_42_33_548Z-debug-0.log", + "stdout": "", + "success": false, + "timedOut": false, } at Object.<anonymous> (src/__functional__/packageManager/packagePublish.test.ts:121:29)
build (ubuntu-latest, node 14, npm 6)
The strategy configuration was canceled because "build.ubuntu-latest_11_20" failed
build (ubuntu-latest, node 14, npm 6)
The operation was canceled.
build (ubuntu-latest, node 20, npm 11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (ubuntu-latest, node 20, npm 11)
No files were found with the provided path: /.npm/_logs. No artifacts will be uploaded.