You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setup go version spec 1.18
Attempting to resolve the latest version from the manifest...
matching 1.18...
Resolved as '1.18.10'
Attempting to download 1.18.10...
matching 1.18.10...
Acquiring 1.18.10 from https://github.com/actions/go-versions/releases/download/1.18.10-3890634278/go-1.18.10-win32-x64.zip
Extracting Go...
Unable to locate executable file: powershell. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
Falling back to download directly from Go
Install from dist
Acquiring go1.18.10 from https://storage.googleapis.com/golang/go1.18.10.windows-amd64.zip
Extracting Go...
Error: Failed to download version 1.18.10: Error: Unable to locate executable file: powershell. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also verify the file has a valid extension for an executable file.
The text was updated successfully, but these errors were encountered:
Hi @dwisiswant0, After trying to replicate the issue based on provided workflow, it appears that everything is functioning correctly and were able to install Go version 1.18.10 successfully without encountering any errors on our end. Here's a screenshot for your reference.
To assist further, could you please share a link to the build or public repository where the issue can be reproduced? This will help us investigate the problem in detail.
Description:
Failed to download version 1.18.10: Error: Unable to locate executable file: powershell.
Action version:
Specify the action version
Platform:
Runner type:
Tools version:
go1.18.x
Repro steps:
Expected behavior:
Successfully set up Go.
Actual behavior:
The text was updated successfully, but these errors were encountered: