cargoless-cas 0.2.0

Content-addressed artifact store: trait + local-disk implementation. Remote backends are v1.
Documentation
  • Coverage
  • 96.43%
    27 out of 28 items documented0 out of 16 items with examples
  • Size
  • Source code size: 54.82 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 650.08 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 4s Average build duration of successful builds.
  • all releases: 4s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • TriformAI/cargoless
    0 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • IggyGG

Content-addressed storage + the build-input hashing that keys it.

The [ContentStore] trait is the v1 remote-backend seam — it MUST exist in v0 even though only [LocalDiskStore] implements it, or v1 becomes a rewrite (decision D10). v0 ships local-disk only; S3/RustFS are v1.

This crate also owns the half of the cargoless-proto contract that cargoless-proto deliberately does not specify: the hash algorithm ([sha256]) and the BuildIdentity → InputHash reduction ([input_hash]) that the whole AC#5 dedupe / AC#4 provenance guarantee rests on. The daemon assembles a BuildIdentity; this crate turns it into the CAS key and stores the bytes.

Concern Where
stable hash primitive [sha256]
BuildIdentity → InputHash, per-file content hashing [identity]
deterministic whole-source-tree hash [tree]
tf clean wipe semantics + safety guard [clean]
artifact byte storage (trait + local disk) [ContentStore]