• v0.10.2 37d70786c3

    v0.10.2
    Some checks failed
    CI / Build / Publish / Shellcheck (push) Successful in 2s
    CI / Build / Publish / Validate CHANGELOG structure (push) Successful in 3s
    CI / Build / Publish / Bats unit tests (push) Successful in 11s
    CI / Build / Publish / PR build & smoke test (push) Has been skipped
    CI / Build / Publish / Host-driven integration (entrypoint + storage sidecars) (push) Successful in 2m7s
    CI / Build / Publish / Round-trip + scheduler smoke (push) Successful in 3m22s
    CI / Build / Publish / Build multi-arch and push (push) Successful in 2m28s
    CI / Build / Publish / Reconcile releases across registries (push) Successful in 1m23s
    CI / Build / Publish / Workflow summary (push) Failing after 0s
    Stable

    Cody Bryant released this 2026-07-21 20:11:18 -07:00 | 0 commits to main since this release

    Changed

    • The automatic recovery kit is no longer written as a locked-down root:600 file. It is already encrypted and lives inside the datastore, so on local and SFTP storage targets it now takes the same ownership and permissions as that storage's own Duplicacy files (matched from the storage's config file on local targets; inherited from the connecting user's umask on SFTP) rather than being a permissions outlier a backup or mirror user cannot read. Object-store targets (B2/S3) are unaffected — they have no POSIX permissions. Existing deployments correct their already-placed kit automatically on the first backup (or archiver recovery-kit) run after upgrade: the kit's placement-scheme version is folded into the change-detection fingerprint, so the one-time re-stamp fires even though the kit content is unchanged — no recovery-kit force needed.

    Dependencies

    • chore(deps): update actions/checkout action to v7.0.1
    • chore(deps): update dependency moby/moby to v29.6.2
    Downloads