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.10.1 d1dc19a068

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

    Cody Bryant released this 2026-07-12 13:48:32 -07:00 | 5 commits to main since this release

    Changed

    • The backup and maintenance pipelines no longer serialize on per-storage locks — they run concurrently, relying on Duplicacy's own lock-free design. Its two-step fossil collection makes a non-exclusive check/prune safe alongside a copy reading or writing the same storage (verified against the Duplicacy v3.2.5 source: a copy reads a mid-prune fossil via a .fsl fallback and writes the destination snapshot last, so a concurrent non-exclusive prune can at worst make a copy abort loudly — never corrupt a storage, delete referenced data, or leave a partial secondary). The practical win: maintenance now runs on its own schedule without waiting for an in-progress copy to finish (previously a copy held the primary storage for its whole duration, so maintenance serialized behind it), and a copy never waits on maintenance. A copy leg that loses that rare race is retried once automatically before being reported as an error. The per-storage lock files (/var/lock/archiver-storage-*) and their healthcheck reporting are removed. Note: this relies on the maintenance pipeline never using prune -exclusive (it uses non-exclusive prune, and -exhaustive — which is safe — never implies -exclusive).
    Downloads