[build] Add Windows arm64 runner#4062
Closed
fhanau wants to merge 3 commits into
Closed
Conversation
fhanau
marked this pull request as draft
May 1, 2025 02:03
Contributor
Author
|
This is blocked for now – rules_js uses yq to parse the pnpm lock file, but doesn't set up a arm64 Windows toolchain for it. https://github.com/bazel-contrib/bazel-lib/blob/main/lib/private/yq_toolchain.bzl |
anonrig
approved these changes
May 1, 2025
fhanau
force-pushed
the
felix/043025-windows-arm64
branch
from
May 3, 2025 22:52
7d89b0e to
c37ee98
Compare
fhanau
force-pushed
the
felix/043025-windows-arm64
branch
from
May 3, 2025 22:52
c37ee98 to
57469f7
Compare
Contributor
Author
|
Managed to patch out the yq issue, but that only revealed several other issues:
This continues to be blocked unfortunately. |
10 tasks
threepointone
added a commit
that referenced
this pull request
Apr 2, 2026
aspect_rules_js uses yq to parse pnpm lockfiles during repository setup.
It resolves the yq binary via @yq_{platform}, where {platform} is detected
from the host. On Windows ARM64, this becomes @yq_windows_arm64, which
doesn't exist in yq.bzl 0.3.2 (the version transitively pulled in by
aspect_rules_js 3.0.3).
yq.bzl 0.3.5 includes Windows ARM64 yq binaries, so we override the
transitive version with a direct bazel_dep in the root MODULE.bazel.
This was the primary blocker identified in the prior Windows ARM64 attempt
(PR #4062). The other blockers from that attempt have since been resolved:
- rules_nodejs 6.7.3 (already used) includes windows_arm64 Node.js
toolchain support (merged in 6.5.0, fix in 6.6.1)
- bazel_lib 3.2.2 (already used) includes windows_arm64 binaries for
copy_to_directory, coreutils, expand_template, and zstd
- The setup-runner action already enables developer mode on Windows via
reg add, which also runs on ARM64 runners
Made-with: Cursor
threepointone
added a commit
that referenced
this pull request
Apr 8, 2026
aspect_rules_js uses yq to parse pnpm lockfiles during repository setup.
It resolves the yq binary via @yq_{platform}, where {platform} is detected
from the host. On Windows ARM64, this becomes @yq_windows_arm64, which
doesn't exist in yq.bzl 0.3.2 (the version transitively pulled in by
aspect_rules_js 3.0.3).
yq.bzl 0.3.5 includes Windows ARM64 yq binaries, so we override the
transitive version with a direct bazel_dep in the root MODULE.bazel.
This was the primary blocker identified in the prior Windows ARM64 attempt
(PR #4062). The other blockers from that attempt have since been resolved:
- rules_nodejs 6.7.3 (already used) includes windows_arm64 Node.js
toolchain support (merged in 6.5.0, fix in 6.6.1)
- bazel_lib 3.2.2 (already used) includes windows_arm64 binaries for
copy_to_directory, coreutils, expand_template, and zstd
- The setup-runner action already enables developer mode on Windows via
reg add, which also runs on ARM64 runners
Made-with: Cursor
threepointone
added a commit
that referenced
this pull request
Apr 8, 2026
aspect_rules_js uses yq to parse pnpm lockfiles during repository setup.
It resolves the yq binary via @yq_{platform}, where {platform} is detected
from the host. On Windows ARM64, this becomes @yq_windows_arm64, which
doesn't exist in yq.bzl 0.3.2 (the version transitively pulled in by
aspect_rules_js 3.0.3).
yq.bzl 0.3.5 includes Windows ARM64 yq binaries, so we override the
transitive version with a direct bazel_dep in the root MODULE.bazel.
This was the primary blocker identified in the prior Windows ARM64 attempt
(PR #4062). The other blockers from that attempt have since been resolved:
- rules_nodejs 6.7.3 (already used) includes windows_arm64 Node.js
toolchain support (merged in 6.5.0, fix in 6.6.1)
- bazel_lib 3.2.2 (already used) includes windows_arm64 binaries for
copy_to_directory, coreutils, expand_template, and zstd
- The setup-runner action already enables developer mode on Windows via
reg add, which also runs on ARM64 runners
Made-with: Cursor
threepointone
added a commit
that referenced
this pull request
Apr 9, 2026
aspect_rules_js uses yq to parse pnpm lockfiles during repository setup.
It resolves the yq binary via @yq_{platform}, where {platform} is detected
from the host. On Windows ARM64, this becomes @yq_windows_arm64, which
doesn't exist in yq.bzl 0.3.2 (the version transitively pulled in by
aspect_rules_js 3.0.3).
yq.bzl 0.3.5 includes Windows ARM64 yq binaries, so we override the
transitive version with a direct bazel_dep in the root MODULE.bazel.
This was the primary blocker identified in the prior Windows ARM64 attempt
(PR #4062). The other blockers from that attempt have since been resolved:
- rules_nodejs 6.7.3 (already used) includes windows_arm64 Node.js
toolchain support (merged in 6.5.0, fix in 6.6.1)
- bazel_lib 3.2.2 (already used) includes windows_arm64 binaries for
copy_to_directory, coreutils, expand_template, and zstd
- The setup-runner action already enables developer mode on Windows via
reg add, which also runs on ARM64 runners
Made-with: Cursor
Contributor
Author
|
Superseded by #6486. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.