Getting Bad Credentials error when passing token input in GHE

[alvaro-ajv]

Description:
When trying to pass the token input to reduce rate limit error, we are getting "Bad Credentials" error; using previous versions of the action it works, but using the last release we get that error.

Seems that the bug was introduced on these PR: 443
Also the same change from the mentioned PR was tested and reverted in these PRs respectively: 427 and 437

Action version 4.2.0 that is before of the change works fine.

We are trying to use the latest version of the action due to deprecation of "set-output" command as described in the docs, and as is mentioned in PR 578, latest version should remove the warning, but we cannot use later versions than 4.2.0 due to above bug.

Bad credentials error:

"set-ouput" warning:

Action version:
Latest

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

[IvanZosimov]

Hi, @alvaro-ajv 👋 Thanks for the issue, we will take a look!

[KFo3]

Similar to Disney's error might be the same bug. Please correct me if I am wrong.
ZD Ticket

Disney just started experiencing this problem after updating GHES to 3.8.3. They are also utilizing PAT over tokens. Self hosted runners using ubuntu:jammy 22.04.2

Current runner version: '2.304.0'

Run actions/setup-python@v4
Version 3.10 was not found in the local cache
Error: Bad credentials

[alvaro-ajv]

@KFo3, yes exactly it's the same bug, it was introduced in this PR: 443

Here the error is happening in Kyndryl's GHE version 3.8.3

[priya-kinthali]

Hello @alvaro-ajv 👋,
Could you kindly verify if the issue related to the rate limit has been resolved and confirm that no other issues have emerged while using the setup-actions-demo/setup-python@main branch.

[priya-kinthali]

Hello @alvaro-ajv 👋,
Just a gentle reminder, Could you kindly verify if the issue related to the rate limit has been resolved and confirm that no other issues have emerged while using the setup-actions-demo/setup-python@main branch.

[priya-kinthali]

Hello @alvaro-ajv 👋,
As part of the latest updates, the potential improvement to leverage the raw API for retrieving version-manifest has been implemented and released in v5.1.0. This new approach should mitigate the rate limit exhaustion without requiring an additional GitHub token.
Please update to the latest version and let us know if you encounter any further issues. As this update resolves the reported problem, we will close this issue.
Thank you!