Skip to content

ci: enforce the hermetic Windows Bazel toolchain#29188

Closed
anp-oai wants to merge 3 commits into
codex/windows-hermetic-native-buildsfrom
codex/windows-hermetic-enforcement
Closed

ci: enforce the hermetic Windows Bazel toolchain#29188
anp-oai wants to merge 3 commits into
codex/windows-hermetic-native-buildsfrom
codex/windows-hermetic-enforcement

Conversation

@anp-oai

@anp-oai anp-oai commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Motivation

Make the Windows Bazel hermeticity boundary fail closed after the gnullvm execution and native-build migrations in #29162.

Implementation

  • remove dead Bazel-only MSVC platforms, flags, and crate/toolchain rewrites
  • sanitize the Windows Bazel client and repository environments before server startup
  • audit declared action tools, frozen build/test paths, gnullvm coverage, native/V8 builds, and the protected C probe
  • run the fixed audit in the Windows Bazel clippy lane

Parent: #29162

Validation

  • focused Windows-gnullvm cross-build of aws-lc-sys, ring, zstd, and the stack-protector probe
  • representative native, V8, and lint aquery graphs passed the hermeticity audit

@anp-oai
anp-oai force-pushed the codex/windows-hermetic-native-builds branch from 3f9b82b to bb0e048 Compare June 22, 2026 17:47
@anp-oai
anp-oai force-pushed the codex/windows-hermetic-enforcement branch from fd90c37 to a725b94 Compare June 22, 2026 18:10
@anp-oai
anp-oai force-pushed the codex/windows-hermetic-native-builds branch 2 times, most recently from f8f4a2f to 7835d1d Compare June 22, 2026 19:28
@anp-oai
anp-oai force-pushed the codex/windows-hermetic-enforcement branch from a725b94 to 7298ce8 Compare June 22, 2026 19:40
@anp-oai anp-oai closed this Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant