Use shared S3 compilation cache for library gates and publishing #11
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/shared-s3-cache-unsigned-sbom"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Common crates remove obsolete signing tooling and enforce the same mandatory Ceph S3 cache for local builds, CI and publishing. Private credentials and a filtered lifecycle/error ledger preserve ownership and detect backend errors across SDK daemon restarts.
Lifecycle and UI tests now observe actual results, states and full cleanup without own wall-clock watchdogs. Actual library defaults and application shutdown contracts remain. Production APIs and behavior are unchanged; the Rust changes are confined to test code.
Validation: complete local just gate exit 0, including 59 cache behavior cases, real Rust/C and SDK lifecycle canaries, the full Rust suite and real browsers. Exact protected CI and publishing checks remain required.