The dbproxy arc gated procid and the force-stop process inspection behind
linux/darwin/windows build tags with no fallback, breaking freebsd/amd64 —
a target every release ships (.goreleaser.yml bd-freebsd-amd64) but no PR
CI cross-compiles, so it surfaced only at the v1.2.0 goreleaser run
(31533013414), which failed pre-publish and burned the tag number.
Both stubs refuse cleanly with a named ErrUnsupported instead of guessing
at process identity: reattach-and-signal without birth identity is exactly
the PID-reuse race these packages exist to close. Ordinary bd use on
freebsd is unaffected — dbproxy machinery has never run there (v1.1.2
shipped freebsd with no dbproxy at all).
Verified: the full release matrix (linux/{amd64,arm64}, android/arm64,
windows/{amd64,arm64}, freebsd/amd64, + darwin/arm64) now cross-compiles
with -tags gms_pure_go; native lint + tests green. CI-gap follow-up (add a
cross-compile check to PR CI) filed separately.