[codex] Build all release targets with Bazel transitions - #27326
Closed
anp-oai wants to merge 1 commit into
Closed
Conversation
anp-oai
force-pushed
the
codex/release-rbe-06-release-matrix
branch
from
June 10, 2026 19:38
e4e7963 to
61559c1
Compare
anp-oai
force-pushed
the
codex/release-rbe-05-arm64-v8-builtins
branch
2 times, most recently
from
June 10, 2026 19:47
0aa36bd to
3c1b89b
Compare
anp-oai
force-pushed
the
codex/release-rbe-06-release-matrix
branch
from
June 10, 2026 19:47
61559c1 to
95e7133
Compare
This was referenced Jun 10, 2026
anp-oai
force-pushed
the
codex/release-rbe-05-arm64-v8-builtins
branch
from
June 11, 2026 01:06
3c1b89b to
3848fdc
Compare
anp-oai
force-pushed
the
codex/release-rbe-06-release-matrix
branch
from
June 11, 2026 01:06
95e7133 to
0eebcc9
Compare
anp-oai
force-pushed
the
codex/release-rbe-05-arm64-v8-builtins
branch
from
June 11, 2026 01:21
3848fdc to
c4f3f10
Compare
anp-oai
force-pushed
the
codex/release-rbe-06-release-matrix
branch
from
June 11, 2026 01:21
0eebcc9 to
3805177
Compare
anp-oai
force-pushed
the
codex/release-rbe-05-arm64-v8-builtins
branch
from
June 11, 2026 18:24
c4f3f10 to
e3cc080
Compare
anp-oai
force-pushed
the
codex/release-rbe-06-release-matrix
branch
from
June 11, 2026 18:24
3805177 to
1f27198
Compare
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
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.
Why
just build-for-releasemust configure six target binaries from one aggregate target while remote execution is enabled. The previousplatform_datawrapper only changed the target platform; source-built V8 also needs a matchingv8_target_cpu, and the release Linux and Windows targets require constraints not present on the corresponding upstream LLVM platforms.What changed
Replace the wrapper with a transition-based executable rule that sets both
//command_line_option:platformsand V8’s target CPU for each binary. Add local Linux musl platforms with non-PIE constraints and Windows platforms with thewindows_gnullvmABI constraint. The macOS targets continue to use the upstream LLVM platforms directly.The aggregate target still exposes the six named release artifacts through
//codex-rs/cli:release_binaries.Validation
just build-for-releaseStack: 6 of 6. Depends on #27325.