Skip to content

Getting error manifest.map is not a function #580

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

Open
2 of 5 tasks
cb80 opened this issue Apr 14, 2025 · 3 comments
Open
2 of 5 tasks

Getting error manifest.map is not a function #580

cb80 opened this issue Apr 14, 2025 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@cb80
Copy link

cb80 commented Apr 14, 2025

Description: Every now and then (but not always) I get the following error in the GitHub workflow logs for the setup-go step:

Setup go version spec stable
Error: manifest.map is not a function

It seems to occur somewhere between these lines https://github.com/actions/setup-go/blob/main/src/main.ts#L21-L45.

What can I do, to analyze this further?

Action version: v5

    - name: Setup Go
      uses: actions/setup-go@v5
      with:
        go-version: stable

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

Tools version:
stable

Repro steps:
It's hard to reproduce and I cannot share the logs, as they reside on a GitHub enterprise instance.

Expected behavior:
No error. latest shall resolve to the latest Go version which is go1.24.2 at the moment.

Actual behavior:
Error occurs while resolving latest.

@cb80 cb80 added bug Something isn't working needs triage labels Apr 14, 2025
@priya-kinthali
Copy link

Hello @cb80👋,
Thank you for reporting this issue. We will investigate it and get back to you as soon as we have some feedback.

@priyagupta108
Copy link
Contributor

Hello @cb80 👋,
We've merged the pull request #586 with possible fix. Could you please try to use actions/setup-go@main to confirm that it works as expected.
Thank you!

@cb80
Copy link
Author

cb80 commented May 9, 2025

Hello @priyagupta108 👋
After our enterprise instance synced the changes, I have not seen the error again. For the moment it looks good, but the error occurred seldomly and it may still be there. If it does not come up again, I will close the GH issue next Friday.
Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants