Skip to content

Releases

v0.9.3

Choose a tag to compare

@github-actions github-actions released this 15 Nov 03:16
4a241c6

Fixed

  • work with Bitwarden's cloud while it hides newer item types (#117)
  • (cli) improve terminal output and recovery guidance

Performance

  • download and store an attachment once across snapshots (#118)

v0.9.2

Choose a tag to compare

@github-actions github-actions released this 26 Oct 04:44
9a03257

Fixed

  • (api) recover interrupted reads and allow slower attachments (#100)

Performance

  • reduce snapshot validation allocations (#101)

v0.9.1

Choose a tag to compare

@github-actions github-actions released this 25 Oct 20:53
2c1bdf5

Fixed

  • protect configuration secrets and update RSA arithmetic (#98)

v0.9.0

Choose a tag to compare

@github-actions github-actions released this 23 Oct 14:10
08524fe

Added

  • (organization) allow updates with accepted metadata loss (#86)

Fixed

  • (setup) honor private CA settings across setup and scheduling (#96)
  • send failure alerts when backup storage is unavailable (#95)
  • (organization) protect copies hidden in member collections (#94)
  • preserve overwrite protection after switching vaults (#93)
  • protect vault data and reject unusable daemon schedules (#92)
  • (setup) validate backup-only logins and setup documentation
  • (notify) send failure alerts when custom CA files are unavailable
  • mount custom CA files and clarify previews
  • (visibility) preserve backups when servers hide item types (#85)
  • (mirror) refuse new copies linked by foreign vault markers (#84)
  • (status) [breaking] distinguish planned work from unverified writes (#83)
  • (mirror) retain verified attachments through archive finalization (#81)
  • (vault) reject encrypted content that cannot be copied (#80)
  • (compose) read settings from the mounted file (#79)
  • (api) hide signed request URLs in debug output (#78)
  • (recovery) [breaking] recover from read-only backups and export portable paths (#75)
  • retain source visibility evidence through planning (#76)
  • validate generated Compose settings on every command (#74)
  • avoid duplicate backups when server lists reorder (#73)
  • reject malformed vault metadata before backup or mirroring (#72)
  • keep rejected server URLs out of diagnostics (#69)

v0.8.1

Choose a tag to compare

@github-actions github-actions released this 18 Oct 16:39
e3492a9

Added

  • (mirror) allow skipping attachments (#66)

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 18 Oct 13:01
7ff3f66

Fixed

  • (organization) preserve member favorites (#65)
  • preserve copy safety and convergence after reversals (#64)
  • [breaking] protect vault data during one-way mirroring (#62)

v0.7.0

Choose a tag to compare

@github-actions github-actions released this 17 Oct 01:26
86ead0f

Changed

  • [breaking] Each snapshot is now one directory in the backup directory.
    Backups made by older versions are no longer read; key.age still works.
    Snapshots older than a day thin out to one a day and expire after
    RETENTION_DAYS, except the newest. An unchanged vault gets no new snapshot.
  • [breaking] Attachments are always backed up and checked after upload.
  • [breaking] Old snapshots are always pruned.

Removed

  • [breaking] MAX_DELETE_PERCENT. A run still stops when it would delete
    every copy or when the source and destination look swapped.
  • [breaking] BACKUP_RECIPIENTS, --identity, run --dry-run,
    INTERVAL (use SCHEDULE), CONCURRENCY, BITWARDEN_CLIENT_VERSION,
    ENABLE_PRUNING, MIN_FILES, the hold files after a failed pull or a
    restore, and the warning about http:// server addresses. After a stopped
    run --pull, runs ask you to run it again. init no longer mounts
    CA_CERT_FILE in compose.yaml.

Fixed

  • run --pull copies back only what changed in the destination, only items the
    filter selects there, and removes only source attachments a backup holds. It
    backs up the destination again afterwards, and refuses to run without a
    destination.
  • Restore checks uploaded attachments by content.
  • Errors about a damaged snapshot no longer quote its content.
  • A run turned away because another one holds the lock no longer overwrites the
    status file or sends a failure notification.
  • init recognizes the source account under any server address.
  • check no longer says your destination edits are backed up.

(#55)

v0.6.1

Choose a tag to compare

@github-actions github-actions released this 16 Oct 19:39
397eeea

Fixed

  • A failed or interrupted run --pull now pauses mirroring until you
    reconcile the vaults. Retrying can no longer copy a partial source write
    over intact destination notes or attachments. This also stops a pull at
    unfinished source items left by an older version.
  • Invalid BACKUP_RECIPIENTS values no longer appear in errors, the status
    file, or failure notifications. This protects a private age key pasted into
    that setting by mistake.
  • Malformed values in known encrypted vault fields now stop the run instead of
    being copied as plaintext.

Documentation

  • Setup now tells you to keep both BACKUP_PASSPHRASE and a separate copy of
    backups/key.age. Recovery needs both. The guide also recommends testing an
    export before relying on the backups.

After a failed pull

The recovery hold remains even after a temporary upload failure or a refusal
before any write. Keep scheduling stopped, preserve both vaults and their
backups, then follow the recovery steps before removing
pull-cleanup-hold.json. A hold protects runs using the same backup
directory.

v0.6.0

Choose a tag to compare

@github-actions github-actions released this 16 Oct 17:10
f5816dc

Fixed

  • [breaking] keep vault data recoverable and protect credentials (#49)

v0.5.3

Choose a tag to compare

@github-actions github-actions released this 16 Oct 11:54
3acd6f0

Fixed

  • warn about attachments changed on both sides before run --pull replaces them (#46)
  • keep an archived item archived when run --pull copies its files (#45)
  • leave out of run --pull what the source server would not show (#44)
  • check run --pull against the safety rules before it changes the source (#43)
  • don't delete a copy that was edited during the run (#42)