borgmatic 1.7.10

• #396: When a database command errors, display and log the error message instead of swallowing it.
• #501: Optionally error if a source directory does not exist via "source_directories_must_exist"
  option in borgmatic's location configuration.
• #576: Add support for "file://" paths within "repositories" option.
• #612: Define and use custom constants in borgmatic configuration files. See the documentation for
  more information:
  https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/#constant-interpolation
• #618: Add support for BORG_FILES_CACHE_TTL environment variable via "borg_files_cache_ttl" option
  in borgmatic's storage configuration.
• #623: Fix confusing message when an error occurs running actions for a configuration file.
• #635: Add optional repository labels so you can select a repository via "--repository yourlabel"
  at the command-line. See the configuration reference for more information:
  https://torsion.org/borgmatic/docs/reference/configuration/
• #649: Add documentation on backing up a database running in a container:
  https://torsion.org/borgmatic/docs/how-to/backup-your-databases/#containers
• #655: Fix error when databases are configured and a source directory doesn't exist.
• Add code style plugins to enforce use of Python f-strings and prevent single-letter variables.
  To join in the pedantry, refresh your test environment with "tox --recreate".
• Rename scripts/run-full-dev-tests to scripts/run-end-to-end-dev-tests and make it run end-to-end
  tests only. Continue using tox to run unit and integration tests.

borgmatic 1.7.9

• #295: Add a SQLite database dump/restore hook.
• #304: Change the default action order when no actions are specified on the command-line to:
  "create", "prune", "compact", "check". If you'd like to retain the old ordering ("prune" and
  "compact" first), then specify actions explicitly on the command-line.
• #304: Run any command-line actions in the order specified instead of using a fixed ordering.
• #564: Add "--repository" flag to all actions where it makes sense, so you can run borgmatic on
  a single configured repository instead of all of them.
• #628: Add a Healthchecks "log" state to send borgmatic logs to Healthchecks without signalling
  success or failure.
• #647: Add "--strip-components all" feature on the "extract" action to remove leading path
  components of files you extract. Must be used with the "--path" flag.
• Add support for Python 3.11.

borgmatic 1.7.8

• #620: With the "create" action and the "--list" ("--files") flag, only show excluded files at
  verbosity 2.
• #621: Add optional authentication to the ntfy monitoring hook.
• With the "create" action, only one of "--list" ("--files") and "--progress" flags can be used.
  This lines up with the new behavior in Borg 2.0.0b5.
• Internally support new Borg 2.0.0b5 "--filter" status characters / item flags for the "create"
  action.
• Fix the "create" action with the "--dry-run" flag querying for databases when a PostgreSQL/MySQL
  "all" database is configured. Now, these queries are skipped due to the dry run.
• Add "--repository" flag to the "rcreate" action to optionally select one configured repository to
  create.
• Add "--progress" flag to the "transfer" action, new in Borg 2.0.0b5.
• Add "checkpoint_volume" configuration option to creates checkpoints every specified number of
  bytes during a long-running backup, new in Borg 2.0.0b5.

borgmatic 1.7.7

• #642: Add MySQL database hook "add_drop_database" configuration option to control whether dumped
  MySQL databases get dropped right before restore.
• #643: Fix for potential data loss (data not getting backed up) when dumping large "directory"
  format PostgreSQL/MongoDB databases. Prior to the fix, these dumps would not finish writing to
  disk before Borg consumed them. Now, the dumping process completes before Borg starts. This only
  applies to "directory" format databases; other formats still stream to Borg without using
  temporary disk space.
• Fix MongoDB "directory" format to work with mongodump/mongorestore without error. Prior to this
  fix, only the "archive" format worked.

borgmatic 1.7.6

• #393, #438, #560: Optionally dump "all" PostgreSQL/MySQL databases to separate files instead of one
  combined dump file, allowing more convenient restores of individual databases. You can enable
  this by specifying the database dump "format" option when the database is named "all".
• #602: Fix logs that interfere with JSON output by making warnings go to stderr instead of stdout.
• #622: Fix traceback when include merging configuration files on ARM64.
• #629: Skip warning about excluded special files when no special files have been excluded.
• #630: Add configuration options for database command customization: "list_options",
  "restore_options", and "analyze_options" for PostgreSQL, "restore_options" for MySQL, and
  "restore_options" for MongoDB.

borgmatic 1.7.5

• #311: Override PostgreSQL dump/restore commands via configuration options.
• #604: Fix traceback when a configuration section is present but lacking any options.
• #607: Clarify documentation examples for include merging and deep merging.
• #611: Fix "data" consistency check to support "check_last" and consistency "prefix" options.
• #613: Clarify documentation about multiple repositories and separate configuration files.

borgmatic 1.7.4

• #596: Fix special file detection erroring when broken symlinks are encountered.
• #597, #598: Fix regression in which "check" action errored on certain systems ("Cannot determine
  Borg repository ID").

borgmatic 1.7.3

• #357: Add "break-lock" action for removing any repository and cache locks leftover from Borg
  aborting.
• #360: To prevent Borg hangs, unconditionally delete stale named pipes before dumping databases.
• #587: When database hooks are enabled, auto-exclude special files from a "create" action to
  prevent Borg from hanging. You can override/prevent this behavior by explicitly setting the
  "read_special" option to true.
• #587: Warn when ignoring a configured "read_special" value of false, as true is needed when
  database hooks are enabled.
• #589: Update sample systemd service file to allow system "idle" (e.g. a video monitor turning
  off) while borgmatic is running.
• #590: Fix for potential data loss (data not getting backed up) when the "patterns_from" option
  was used with "source_directories" (or the "~/.borgmatic" path existed, which got injected into
  "source_directories" implicitly). The fix is for borgmatic to convert "source_directories" into
  patterns whenever "patterns_from" is used, working around a Borg bug:
  borgbackup/borg#6994
• #590: In "borgmatic create --list" output, display which files get excluded from the backup due
  to patterns or excludes.
• #591: Add support for Borg 2's "--match-archives" flag. This replaces "--glob-archives", which
  borgmatic now treats as an alias for "--match-archives". But note that the two flags have
  slightly different syntax. See the Borg 2 changelog for more information:
  https://borgbackup.readthedocs.io/en/2.0.0b3/changes.html#version-2-0-0b3-2022-10-02
• Fix for "borgmatic --archive latest" not finding the latest archive when a verbosity is set.

borgmatic 1.7.2

• #577: Fix regression in which "borgmatic info --archive ..." showed repository info instead of
  archive info with Borg 1.
• #582: Fix hang when database hooks are enabled and "patterns" contains a parent directory of
  "~/.borgmatic".

borgmatic 1.7.1

• #542: Make the "source_directories" option optional. This is useful for "check"-only setups or
  using "patterns" exclusively.
• #574: Fix for potential data loss (data not getting backed up) when the "patterns" option was
  used with "source_directories" (or the "~/.borgmatic" path existed, which got injected into
  "source_directories" implicitly). The fix is for borgmatic to convert "source_directories" into
  patterns whenever "patterns" is used, working around a potential Borg bug:
  borgbackup/borg#6994