Borgmatic

Latest version: v1.9.5

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

Scan your dependencies

Page 4 of 29

1.8.2

Not secure
* 345: Add "key export" action to export a copy of the repository key for safekeeping in case
the original goes missing or gets damaged.
* 727: Add a MariaDB database hook that uses native MariaDB commands instead of the deprecated
MySQL ones. Be aware though that any existing backups made with the "mysql_databases:" hook are
only restorable with a "mysql_databases:" configuration.
* 738: Fix for potential data loss (data not getting restored) in which the database "restore"
action didn't actually restore anything and indicated success anyway.
* Remove the deprecated use of the MongoDB hook's "--db" flag for database restoration.
* Add source code reference documentation for getting oriented with the borgmatic code as a
developer: https://torsion.org/borgmatic/docs/reference/source-code/

1.8.1

Not secure
* 326: Add documentation for restoring a database to an alternate host:
https://torsion.org/borgmatic/docs/how-to/backup-your-databases/#restore-to-an-alternate-host
* 697: Add documentation for "bootstrap" action:
https://torsion.org/borgmatic/docs/how-to/extract-a-backup/#extract-the-configuration-files-used-to-create-an-archive
* 725: Add "store_config_files" option for disabling the automatic backup of configuration files
used by the "config bootstrap" action.
* 728: Fix for "prune" action error when using the "keep_exclude_tags" option.
* 730: Fix for Borg's interactive prompt on the "check --repair" action automatically getting
answered "NO" even when the "check_i_know_what_i_am_doing" option isn't set.
* 732: Include multiple configuration files with a single "!include". See the documentation for
more information:
https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/#multiple-merge-includes
* 734: Omit "--glob-archives" or "--match-archives" Borg flag when its value would be "*" (meaning
all archives).

1.8.0

Not secure
* 575: BREAKING: For the "borgmatic borg" action, instead of implicitly injecting
repository/archive into the resulting Borg command-line, pass repository to Borg via an
environment variable and make archive available for explicit use in your commands. See the
documentation for more information:
https://torsion.org/borgmatic/docs/how-to/run-arbitrary-borg-commands/
* 719: Fix an error when running "borg key export" through borgmatic.
* 720: Fix an error when dumping a database and the "exclude_nodump" option is set.
* 724: Add "check_i_know_what_i_am_doing" option to bypass Borg confirmation prompt when running
"check --repair".
* When merging two configuration files, error gracefully if the two files do not adhere to the same
format.
* 721: Remove configuration sections ("location:", "storage:", "hooks:", etc.), while still
keeping deprecated support for them. Now, all options are at the same level, and you don't need
to worry about commenting/uncommenting section headers when you change an option (if you remove
your sections first).
* 721: BREAKING: The retention prefix and the consistency prefix can no longer have different
values (unless one is not set).
* 721: BREAKING: The storage umask and the hooks umask can no longer have different values (unless
one is not set).
* BREAKING: Flags like "--config" that previously took multiple values now need to be given once
per value, e.g. "--config first.yaml --config second.yaml" instead of "--config first.yaml
second.yaml". This prevents argument parsing errors on ambiguous commands.
* BREAKING: Remove the deprecated (and silently ignored) "--successful" flag on the "list" action,
as newer versions of Borg list successful (non-checkpoint) archives by default.
* All deprecated configuration option values now generate warning logs.
* Remove the deprecated (and non-functional) "--excludes" flag in favor of excludes within
configuration.
* Fix an error when logging too-long command output during error handling. Now, long command output
is truncated before logging.

1.7.15

Not secure
* 326: Add configuration options and command-line flags for backing up a database from one
location while restoring it somewhere else.
* 399: Add a documentation troubleshooting note for MySQL/MariaDB authentication errors.
* 529: Remove upgrade-borgmatic-config command for upgrading borgmatic 1.1.0 INI-style
configuration.
* 529: Deprecate generate-borgmatic-config in favor of new "config generate" action.
* 529: Deprecate validate-borgmatic-config in favor of new "config validate" action.
* 697, 712, 716: Extract borgmatic configuration from backup via new "config bootstrap"
action—even when borgmatic has no configuration yet!
* 669: Add sample systemd user service for running borgmatic as a non-root user.
* 711, 713: Fix an error when "data" check time files are accessed without getting upgraded
first.

1.7.14

Not secure
* 484: Add a new verbosity level (-2) to disable output entirely (for console, syslog, log file,
or monitoring), so not even errors are shown.
* 688: Tweak archive check probing logic to use the newest timestamp found when multiple exist.
* 659: Add Borg 2 date-based matching flags to various actions for archive selection.
* 703: Fix an error when loading the configuration schema on Fedora Linux.
* 704: Fix "check" action error when repository and archive checks are configured but the archive
check gets skipped due to the configured frequency.
* 706: Fix "--archive latest" on "list" and "info" actions that only worked on the first of
multiple configured repositories.

1.7.13

Not secure
* 375: Restore particular PostgreSQL schemas from a database dump via "borgmatic restore --schema"
flag. See the documentation for more information:
https://torsion.org/borgmatic/docs/how-to/backup-your-databases/#restore-particular-schemas
* 678: Fix error from PostgreSQL when dumping a database with a "format" of "plain".
* 678: Fix PostgreSQL hook to support "psql_command" and "pg_restore_command" options containing
commands with arguments.
* 678: Fix calls to psql in PostgreSQL hook to ignore "~/.psqlrc", whose settings can break
database dumping.
* 680: Add support for logging each log line as a JSON object via global "--log-json" flag.
* 682: Fix "source_directories_must_exist" option to expand globs and tildes in source directories.
* 684: Rename "master" development branch to "main" to use more inclusive language. You'll need to
update your development checkouts accordingly.
* 686: Add fish shell completion script so you can tab-complete on the borgmatic command-line. See
the documentation for more information:
https://torsion.org/borgmatic/docs/how-to/set-up-backups/#shell-completion
* 687: Fix borgmatic error when not finding the configuration schema for certain "pip install
--editable" development installs.
* 688: Fix archive checks being skipped even when particular archives haven't been checked
recently. This occurred when using multiple borgmatic configuration files with different
"archive_name_format"s, for instance.
* 691: Fix error in "borgmatic restore" action when the configured repository path is relative
instead of absolute.
* 694: Run "borgmatic borg" action without capturing output so interactive prompts and flags like
"--progress" still work.

Page 4 of 29

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.