borgmatic 1.5.7

• #327: Fix broken pass-through of BORG_* environment variables to Borg.
• #328: Fix duplicate logging to Healthchecks and send "after_*" hooks output to Healthchecks.
• #331: Add SSL support to PostgreSQL database configuration.
• #333: Fix for potential data loss (data not getting backed up) when borgmatic omitted configured
  source directories in certain situations. Specifically, this occurred when two source directories
  on different filesystems were related by parentage (e.g. "/foo" and "/foo/bar/baz") and the
  one_file_system option was enabled.
• Update documentation code fragments theme to better match the rest of the page.
• Improve configuration reference documentation readability via more aggressive word-wrapping in
  configuration schema descriptions.

borgmatic 1.5.6

• #292: Allow before_backup and similiar hooks to exit with a soft failure without altering the
  monitoring status on Healthchecks or other providers. Support this by waiting to ping monitoring
  services with a "start" status until after before_* hooks finish. Failures in before_* hooks
  still trigger a monitoring "fail" status.
• #316: Fix hang when a stale database dump named pipe from an aborted borgmatic run remains on
  disk.
• #323: Fix for certain configuration options like ssh_command impacting Borg invocations for
  separate configuration files.
• #324: Add "borgmatic extract --strip-components" flag to remove leading path components when
  extracting an archive.
• Tweak comment indentation in generated configuration file for clarity.
• Link to Borgmacator GNOME AppIndicator from monitoring documentation.

borgmatic 1.5.5

• #314: Fix regression in support for PostgreSQL's "directory" dump format. Unlike other dump
  formats, the "directory" dump format does not stream directly to/from Borg.
• #315: Fix enabled database hooks to implicitly set one_file_system configuration option to true.
  This prevents Borg from reading devices like /dev/zero and hanging.
• #316: Fix hang when streaming a database dump to Borg with implicit duplicate source directories
  by deduplicating them first.
• #319: Fix error message when there are no MySQL databases to dump for "all" databases.
• Improve documentation around the installation process. Specifically, making borgmatic commands
  runnable via the system PATH and offering a global install option.

borgmatic 1.5.4

• #310: Fix legitimate database dump command errors (exit code 1) not being treated as errors by
  borgmatic.
• For database dumps, replace the named pipe on every borgmatic run. This prevent hangs on stale
  pipes left over from previous runs.
• Fix error handling to handle more edge cases when executing commands.

borgmatic 1.5.3

• #258: Stream database dumps and restores directly to/from Borg without using any additional
  filesystem space. This feature is automatic, and works even on restores from archives made with
  previous versions of borgmatic.
• #293: Documentation on macOS launchd permissions issues with work-around for Full Disk Access.
• Remove "borgmatic restore --progress" flag, as it now conflicts with streaming database restores.

borgmatic 1.5.2

• #301: Fix MySQL restore error on "all" database dump by excluding system tables.
• Fix PostgreSQL restore error on "all" database dump by using "psql" for the restore instead of
  "pg_restore".

borgmatic 1.5.1

• #289: Tired of looking up the latest successful archive name in order to pass it to borgmatic
  actions? Me too. Now you can specify "--archive latest" to all actions that accept an archive
  flag.
• #290: Fix the "--stats" and "--files" flags so that they yield output at verbosity 0.
• Reduce the default verbosity of borgmatic logs sent to Healthchecks monitoring hook. Now, it's
  warnings and errors only. You can increase the verbosity via the "--monitoring-verbosity" flag.
• Add security policy documentation in SECURITY.md.

borgmatic 1.5.0

• #245: Monitor backups with PagerDuty hook integration. See the documentation for more
  information: https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#pagerduty-hook
• #255: Add per-action hooks: "before_prune", "after_prune", "before_check", and "after_check".
• #274: Add ~/.config/borgmatic.d as another configuration directory default.
• #277: Customize Healthchecks log level via borgmatic "--monitoring-verbosity" flag.
• #280: Change "exclude_if_present" option to support multiple filenames that indicate a directory
  should be excluded from backups, rather than just a single filename.
• #284: Backup to a removable drive or intermittent server via "soft failure" feature. See the
  documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/backup-to-a-removable-drive-or-an-intermittent-server/
• #287: View consistency check progress via "--progress" flag for "check" action.
• For "create" and "prune" actions, no longer list files or show detailed stats at any verbosities
  by default. You can opt back in with "--files" or "--stats" flags.
• For "list" and "info" actions, show repository names even at verbosity 0.

🎆

borgmatic 1.4.22

• #276, #285: Disable colored output when "--json" flag is used, so as to produce valid JSON ouput.
• After a backup of a database dump in directory format, properly remove the dump directory.
• In "borgmatic --help", don't expand $HOME in listing of default "--config" paths.

borgmatic 1.4.21

• #268: Override particular configuration options from the command-line via "--override" flag. See
  the documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/#configuration-overrides
• #270: Only trigger "on_error" hooks and monitoring failures for "prune", "create", and "check"
  actions, and not for other actions.
• When pruning with verbosity level 1, list pruned and kept archives. Previously, this information
  was only shown at verbosity level 2.