1.1.7

fix big files timing out, one bad folder aborting the whole backup, and failed daily backups never retrying

1.1.6

keep the computer awake while a backup runs A machine that goes to sleep mid-backup suspends Obsidian with it and leaves a half-copied snapshot until it wakes. The scheduled daily backup, running when nobody is at the keyboard, is the one most likely to hit the idle timeout.

1.1.5

default to daily-only backups, keep 3d/4w/12mo

1.1.4

add "Buy me a cookie" support link to settings

1.1.3

Two bugs found in a full review of the backup path, plus 1.1.2's retention fix:

• Retention deletes now retry on transient filesystem errors (ENOTEMPTY/EBUSY/EPERM), which on a network drive could previously abort a delete partway through and silently orphan a backup folder forever (1.1.2).
• The daily schedule required an exact HH:MM match, so sleep, a closed app, or a missed tick could skip a whole day's backup. It now catches up automatically — and skips the catch-up run if a backup from any other trigger (startup/manual/hourly) already ran that day, avoiding a redundant full-vault copy.
• File copying could race its own 60s timeout: a timed-out copy could still be writing to the destination while a retry started a second copy to the same path, risking a corrupted backup file on a slow/flaky drive. Each attempt now copies to a unique temp file and moves it into place atomically.

9 new tests cover all three fixes (32 total, all passing).

1.1.1

Fixes a bug in the 1.1.0 release: the published main.js required a backup-core.js module that was never attached as a release asset, so the plugin failed to load however it was installed (manual copy, BRAT, or the community plugin browser). main.js is now bundled into a single self-contained file at build time — no functional/behavior changes from 1.1.0.

1.1.0

Accumulated changes since 1.0.0: backup execution now runs in-process (no spawned child), daily backup defaults to 20:00 and also runs on startup, "run on shutdown" removed, and several correctness/robustness fixes. Internally, the backup/retention logic was split into backup-core.js and covered by an automated test suite (22 tests) verifying the daily/weekly/monthly retention policy.

1.0.0

Initial release: back up the vault to a chosen folder, versioned by date/time, via a low-priority background process, with configurable daily/weekly/monthly retention and startup/shutdown/hourly/daily scheduling.