jif b75d1e8966 Use a dedicated binary for Bazel schema generation (#58083) ...

## Why

The schema exporter sits on application builds' critical path, but compiling it as a test harness also compiles and registers unit tests that schema generation does not need.

## What changed

Build the exporter with `--cfg=test` to retain test-only schema derives without the test harness, and disable its debug metadata. Run schema generation directly on a thread with an 8 MiB stack.

Share the environment-driven schema writer with the existing ignored test, allow a configurable crate root in `schema_sources`, and switch the public schema bundle to the dedicated generator.

GitOrigin-RevId: 317e24f77e153b9ba0c5c583837eed3bcd3774fd

2026-10-29 13:37:06 +00:00

..

testing

Support close-on-exec attachments without changing PTY semantics (#47797)

2026-09-24 09:25:19 +00:00

BUILD.bazel

Add Bazel release staging archives (#51850)

2026-10-07 22:11:14 +00:00

e2e_benchmark.bzl

bench: add codex help e2e macrobenchmark (#31295)

2026-07-09 17:23:44 -07:00

runtime_package.bzl

Build V8 from source by default in Bazel (#57832)

2026-10-28 20:57:54 +00:00

schema_bundle.bzl

Use a dedicated binary for Bazel schema generation (#58083)

2026-10-29 13:37:06 +00:00