Integrate owned blocking, shared cache and verified unsigned VRDS releases #344
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?
Native audio, payload processing and atomic filesystem commits use the published Common blocking owner, keeping HTTP and probes responsive. Cancellation retains actual jobs, locks and temporary resources through join; finite SDK initialization/session writes finish before SDK store close. The implemented integration and already approved main lockfile maintenance are preserved.
Release now executes the actual candidate before promotion: linux/amd64, its own UID/GID65532, read-only root, fresh owned volumes, HTTP/configuration processing and SIGTERM exit0. Unsigned SPDX remains digest-bound in the existing Harbor repository with subject/byte verification; only that accepted digest becomes version/latest. Shared Ceph S3 and Docker caches remain in use. No report artifacts or own processing/test deadlines.
Validation: complete local just gate exit0 (410 Rust executions including 363 library cases, real native audio/API/browser/PG-LID and optimized worker canary; deny/machete0). The new image acceptance passed on the released 3.6.10 digest both locally and on the Linux runner, with owned resource cleanup. CI1349 already accepted
8405a8c; required CI validates the additional release-check commit. All110 functions and historical image/data/restore/rollback evidence are retained. Production GitOps switching is separate; the optional live OpenCloud test requires its own account.Use shared S3 compilation cache and unsigned Harbor SBOMsto Align release, cache and blocking runtime with Rust standardAlign release, cache and blocking runtime with Rust standardto Integrate owned blocking, shared cache and verified unsigned VRDS releases