2026.9.24.2's publish failed on failed to read /build/vendor/sieve-rs/Cargo.toml in cargo chef cook: #27 put vendor/ in the build context, but the builder stage cooks the dependencies before it copies the tree in. It now copies vendor/ before the cook. context-check.py also checks that each patched path reaches the cook stage, and fails on the old Dockerfile.
The second commit bumps to 2026.9.24.3, since the 2026.9.24.2 tag never published.
Upstream files
Dockerfile: one COPY line, marked inbuxa:.
Clean room
Not applicable.
Testing
A local docker buildx build --target builder got past the cook step into compiling dependencies (755 crates, stopped on purpose). context-check.py passes with the fix and fails without it.
## Summary
2026.9.24.2's publish failed on `failed to read /build/vendor/sieve-rs/Cargo.toml` in `cargo chef cook`: #27 put vendor/ in the build context, but the builder stage cooks the dependencies before it copies the tree in. It now copies vendor/ before the cook. context-check.py also checks that each patched path reaches the cook stage, and fails on the old Dockerfile.
The second commit bumps to 2026.9.24.3, since the 2026.9.24.2 tag never published.
## Upstream files
Dockerfile: one COPY line, marked `inbuxa:`.
## Clean room
Not applicable.
## Testing
A local `docker buildx build --target builder` got past the cook step into compiling dependencies (755 crates, stopped on purpose). context-check.py passes with the fix and fails without it.
#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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
2026.9.24.2's publish failed on
failed to read /build/vendor/sieve-rs/Cargo.tomlincargo chef cook: #27 put vendor/ in the build context, but the builder stage cooks the dependencies before it copies the tree in. It now copies vendor/ before the cook. context-check.py also checks that each patched path reaches the cook stage, and fails on the old Dockerfile.The second commit bumps to 2026.9.24.3, since the 2026.9.24.2 tag never published.
Upstream files
Dockerfile: one COPY line, marked
inbuxa:.Clean room
Not applicable.
Testing
A local
docker buildx build --target buildergot past the cook step into compiling dependencies (755 crates, stopped on purpose). context-check.py passes with the fix and fails without it.