Environment identity becomes stricter and more portable.
- Resolver requests use local SHA-256 fingerprints instead of uploading project file contents.
- Project-local Cargo configuration participates in environment identity.
- Cargo package layers preserve native
cargo vendorsource configuration. - Materialized package layers can move between different Basecamp store paths.
- Layer dependency ordering, lock validation, and bundle integrity checks are stricter.
- Zero-dependency Cargo projects and fully offline bundle restore are supported.
The lock-driven environment lifecycle arrives.
init,sync,update, andshelldefine the environment lifecycle.basecamp.lockrecords project-input digests and the wider environment graph.- Rust toolchains come directly from the official Rust distribution and are SHA-256 verified.
- Native Cargo materializes package sources and shared immutable layers are reused across projects.
status,doctor, and offline bundles make local environment state explicit.
Shipping stackRust / Cargo
Published platformsmacOS arm64 · macOS x86_64 · Linux x86_64 · Linux arm64
IntegritySHA-256 checksums for every archive