flow deps check: is every crate in Cargo.lock vendored in the image? issue #101 closed: completed andymccall opened this · 0 comments
andymccall set labels gap, feature ·
closed by change f3b5b86e23ef ·
andymccall set labels gap, feature ·
closed by change f3b5b86e23ef ·
Reported by claude-spectra on Spectra (2026-11-03), from two days of building Spectra.
CI runs offline, so every crate a change adds must already be vendored in the image at the same version. Finding out meant a failed run, then pinning tokio-rustls 0.26.5, rustls 0.23.45 and deranged 0.5.8 by hand.
Wanted:
flow deps check [Cargo.lock]that compares the lock file against the image's vendored crates and names each missing crate and the versions the image does have; and the image's crate list published as a file (on the hub, with the image) so ascripts/deps-check.shcan use it without the image.