Skip to main content

report_build_provenance

Function report_build_provenance 

Source
pub fn report_build_provenance()
Expand description

Record how this binary was built, so a drifted one says so instead of being silent.

Call once at startup after tracing init. The Cargo.lock digest is reported alongside because it catches a build that honoured a locally-modified one, which provenance cannot see because the guard did run. It only means something compared against a build of the released tag - a bare digest in a log is not self-evidently correct, and being FNV-1a it will not match shasum.