You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Please find the configured pipeline below
Find Error below from the pipeline
npm verb stack Error: This command requires you to be logged in to $NPM_REGISTRY
npm verb stack at Publish.exec (/usr/local/lib/node_modules/npm/lib/commands/publish.js:110:29)
npm verb stack at async module.exports (/usr/local/lib/node_modules/npm/lib/cli-entry.js:61:5)
npm verb cwd /opt/atlassian/pipelines/agent/build
npm verb Linux 5.15.0-1044-aws
npm verb node v18.18.0
npm verb npm v9.8.1
npm ERR! code ENEEDAUTH
npm ERR! need auth This command requires you to be logged in to $NPM_REGISTRY
npm ERR! need auth You need to authorize this machine using `npm adduser`
npm verb exit 1
npm verb code 1
npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2023-10-17T08_46_19_082Z-debug-0.log
+ set -e
+ [[ 1 -eq 0 ]]
+ fail 'Failed to publish package "@email@example.com".'
+ echo -e '\e[31m✖ Failed to publish package "@firstname.lastname@example.org".\e[0m'
+ exit 1
Hi Pranshu and welcome to the community!
The README of the pipe's repo mentions the following:
Are you publishing to a registry other than https://npmjs.com/? If so, have you configured the publishConfig.registry key in your package.json?