Sean Huang 108cf2975a Enforce V8 artifact profiles at Bazel target boundaries (#57165) ...

## Why

V8 source and release artifacts require different ABI and C++ runtime settings. Selecting a named artifact should also select its required settings, without callers coordinating separate sandbox, pointer compression, libc++, and CPU flags.

## What changed

- Add Bazel transitions for `source`, `release`, and `sandbox_release` profiles. Source builds use the sandbox ABI and workspace runtime; release pairs use Chromium's pinned runtime with their respective ABI.
- Select the V8 CPU from the artifact target and enforce matching target platform constraints.
- Make the underlying V8 settings unavailable as CLI flags and remove redundant configuration from release tooling and workflows.
- Select Darwin/Linux prebuilts solely through `rusty_v8_from_source`, keeping source archives and bindings paired when enabled.

GitOrigin-RevId: f72fc06b6f74b79ab2ab8ca697e4f2006076a833

2026-10-26 17:56:15 +00:00

..

powershell

bazel: add PowerShell to Wine test harness (#28120)

2026-06-14 04:52:32 +00:00

v8

Enforce V8 artifact profiles at Bazel target boundaries (#57165)

2026-10-26 17:56:15 +00:00

voice

Align Bazel release builds with Cargo and fix platform compatibility (#51848)

2026-10-07 22:10:23 +00:00

wezterm

Vendor ConPtySystem (#7656)

2025-12-09 17:23:51 +00:00

wine

[codex] Add hermetic Wine test support (#27964)

2026-06-12 18:24:49 -07:00