Fix setup-bazel for Windows ARM64 #28
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
p0deje
force-pushed
the
p0deje/fix-windows-arm64
branch
from
054d75a to
273e977
Compare
|
Closing per #25 (comment) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #25
Implements a workaround for using Bazelisk on Windows ARM64 GitHub runners by temporarily using the x64 architecture binary until an ARM64 version becomes available. This change addresses the issue where setup-bazel failed to function correctly on Windows ARM64 due to the absence of a compatible Bazelisk binary.
downloadBazeliskfunction inindex.jsto check the platform and architecture. If it's Windows (win32) and ARM64, it sets the architecture toamd64to download the x64 binary as a temporary workaround.index.jsexplaining the temporary workaround for ARM64 on Windows and references the related Bazelisk GitHub issue for context.README.mdto include a note for Windows ARM64 users, explaining the temporary use of x64 Bazelisk binary and linking to the Bazelisk issue for more details.For more details, open the Copilot Workspace session.