Unable to publish a private package to github repository #119948
Replies: 3 comments 2 replies
-
There haven't been any changes that I'd think would effect this - the first time you noticed it occur, did you use a different token than the one you used back when it was working? |
Beta Was this translation helpful? Give feedback.
-
The same error here. Two months ago the package was published normally, but this week I'm receiving the same unauthorized error.
|
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Hi Team, i am unable to publish the package to our private github repository using github workflow actions. I am able to publish the same package a month ago and now my pipeline is failing with below error and there are no changes to our workflow actions.
npm notice Publishing to https://npm.pkg.github.com/ with tag latest and default access
npm ERR! code E401
npm ERR! 401 Unauthorized - PUT https://npm.pkg.github.com/@xyzzzzzz%2fdata-access - unauthenticated: User cannot be authenticated with the token provided.
I have regenerated the token and used the new token in workflow but still the same issue. Please let me know are there any changes in last month which has caused this failure.
Beta Was this translation helpful? Give feedback.
All reactions