Borgmatic

Latest version: v1.9.5

Safety actively analyzes 693883 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 11 of 29

1.5.8

Not secure
* 336: Fix for traceback when running Cronitor, Cronhub, and PagerDuty monitor hooks.

1.5.7

Not secure
* 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.

1.5.6

Not secure
* 292: Allow before_backup and similar 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.

1.5.5

Not secure
* 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.

1.5.4

Not secure
* 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.

1.5.3

Not secure
* 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.

Page 11 of 29

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.