Summary
Binding Release Candidate still recompiles natives with maturin/napi (Cargo graph) while PR CI already builds //:binding_cdylibs and assembles via scripts/ci/assemble_bazel_binding_packages.py. Publish authority should be Bazel-built bytes.
Acceptance criteria
Non-goals
- Linux aarch64 wheel + sdist install test (follow-on)
- Moving Clippy/fuzz/crates.io publish onto Bazel
BDD
- Given Binding RC runs on a cut-over platform, When packages are assembled, Then natives come from Bazel
//:binding_cdylibs without maturin build / napi build recompile
- Given assembler argv, When it looks like a silent recompile, Then the assembler refuses
Source
Devinfra Audit Fix-It Plan Wave D / PR11
Summary
Binding Release Candidate still recompiles natives with maturin/napi (Cargo graph) while PR CI already builds
//:binding_cdylibsand assembles viascripts/ci/assemble_bazel_binding_packages.py. Publish authority should be Bazel-built bytes.Acceptance criteria
binding-release-candidate.ymlbuilds Bazel cdylibs and assembles packages viaassemble_bazel_binding_packages.pyfor at least Linux; prefer full matrix cutover if workabledocs/development/bazel-migration-cutover.md(and release-process as needed)target/on artifact-producing lanes once hermetic where applicableNon-goals
BDD
//:binding_cdylibswithoutmaturin build/napi buildrecompileSource
Devinfra Audit Fix-It Plan Wave D / PR11