Skip to content

ci: Binding RC consumes Bazel-built natives via assembler #450

Description

@DecisionNerd

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

  • binding-release-candidate.yml builds Bazel cdylibs and assembles packages via assemble_bazel_binding_packages.py for at least Linux; prefer full matrix cutover if workable
  • Stop maturin/napi recompile of a second graph where feasible on cut-over lanes
  • Update docs/development/bazel-migration-cutover.md (and release-process as needed)
  • Shrink/retire Linux sticky target/ on artifact-producing lanes once hermetic where applicable

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions