SisyphusMD/archiver
1
0
Fork 0
Code Issues 1 Pull requests 1 Projects Releases 40 Packages 1 Wiki Activity Actions
40 releases 40 tags
  • v0.9.1 c84fbf7d28

    v0.9.1
    All checks were successful
    CI / Build / Publish / Shellcheck (push) Successful in 6s
    Details
    CI / Build / Publish / Validate CHANGELOG structure (push) Successful in 3s
    Details
    CI / Build / Publish / Bats unit tests (push) Successful in 13s
    Details
    CI / Build / Publish / PR build & smoke test (push) Has been skipped
    Details
    CI / Build / Publish / Round-trip + scheduler smoke (push) Successful in 5m18s
    Details
    CI / Build / Publish / Host-driven integration (entrypoint + storage sidecars) (push) Successful in 6m42s
    Details
    CI / Build / Publish / Build multi-arch and push (push) Successful in 5m20s
    Details
    CI / Build / Publish / Reconcile releases across registries (push) Successful in 2m38s
    Details
    CI / Build / Publish / Workflow summary (push) Successful in 1s
    Details
    Stable

    Cody Bryant released this 2026-07-10 14:58:22 -07:00 | 27 commits to main since this release

    Changed

    • archiver init now writes its output (the env-native/ materials and the escrow bundle.tar.enc) to a neutral /opt/archiver/setup directory — mount that for init (-v ./archiver-setup:/opt/archiver/setup). Bundle-mode deployments still mount the bundle at /opt/archiver/bundle at run time; only the init output location moved, so the primary setup flow is no longer branded by the transitional bundle path. init also no longer claims the bundle is required to run Archiver (it is the disaster-recovery escrow).
    • Image-build robustness: the three binary downloads (duplicacy, docker-cli, supercronic) retry on transient network errors instead of failing the whole build on a single reset, and the docker-cli archive is downloaded to a file before extraction.
    Downloads