jcoffey-dev 30df055e39 Image build: put the vendored crate where cargo chef cooks ...

#27 let the build context see vendor/, but the Dockerfile cooks the
dependencies before it copies the tree, from a recipe that carries only the
workspace's manifests. [patch.crates-io] points sieve-rs at vendor/, so the
cook failed the same way: failed to read /build/vendor/sieve-rs/Cargo.toml.
That's why 2026.9.24.2's publish failed. The builder stage now copies
vendor/ before cooking; a local build got past it into compiling the
dependencies.

context-check.py now also checks that each patched path is copied into the
cooking stage before the cook, and fails on the Dockerfile as it was.

2026-09-22 23:04:50 -07:00

..

fork

Image build: put the vendored crate where cargo chef cooks

2026-09-22 23:04:50 -07:00