Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Workflow Labeler fails with error: npm error Unable to authenticate, your authentication token seems to be invalid. #20732

Open
4 of 8 tasks
abatishchev opened this issue Dec 15, 2024 · 3 comments

Comments

@abatishchev
Copy link

abatishchev commented Dec 15, 2024

New issue checklist

Task name

N/A

Task version

N/A

Issue Description

Error:

npm error code E401
npm error Unable to authenticate, your authentication token seems to be invalid.
npm error To correct this please try logging in again with:
npm error   npm login

See https://github.com/microsoft/azure-pipelines-tasks/actions/runs/12340684271/job/34438443983#step:5:43

See also:

1.#18732
2. #17253

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container
  • N/A

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

N/A

Operation system

N/A

Relevant log output

N/A

Full task logs with system.debug enabled

N/A

Repro steps

N/A

@abatishchev
Copy link
Author

abatishchev commented Dec 16, 2024

Hi @v-schhabra,
Does every user who opens an issue in this repo need to create a token for the repo's housekeeping workflow (per my understanding what the Labeler does) could function?

@v-schhabra
Copy link
Contributor

v-schhabra commented Dec 16, 2024

Hi @abatishchev
No, users don’t need to create tokens for such workflows to function.

@abatishchev
Copy link
Author

Hi @v-schhabra,
I'm like a regular user then. I just filed an issue in this repo and noticed the Labeler workflow has failed, hence filed this one.
Makes sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants