Repository navigation
Releases
Releases · NikitaMGrimm/vault-mirror
v0.9.3
v0.9.2
v0.9.1
Fixed
- protect configuration secrets and update RSA arithmetic (#98)
v0.9.0
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
Added
- (mirror) allow skipping attachments (#66)
v0.8.0
v0.7.0
Changed
- [breaking] Each snapshot is now one directory in the backup directory.
Backups made by older versions are no longer read;key.agestill 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(useSCHEDULE),CONCURRENCY,BITWARDEN_CLIENT_VERSION,
ENABLE_PRUNING,MIN_FILES, the hold files after a failed pull or a
restore, and the warning abouthttp://server addresses. After a stopped
run --pull, runs ask you to run it again.initno longer mounts
CA_CERT_FILEincompose.yaml.
Fixed
run --pullcopies 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. initrecognizes the source account under any server address.checkno longer says your destination edits are backed up.
(#55)
v0.6.1
Fixed
- A failed or interrupted
run --pullnow 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_RECIPIENTSvalues 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_PASSPHRASEand 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
Fixed
- [breaking] keep vault data recoverable and protect credentials (#49)
v0.5.3
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)