borgmatic 1.9.8

• #979: Fix root patterns so they don't have an invalid "sh:" prefix before getting passed to Borg.
• Expand the recent contributors documentation section to include ticket submitters—not just code
  contributors—because there are multiple ways to contribute to the project! See:
  https://torsion.org/borgmatic/#recent-contributors

borgmatic 1.9.7

• #855: Add a Sentry monitoring hook. See the documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#sentry-hook
• #968: Fix for a "spot" check error when a filename in the most recent archive contains a newline.
• #970: Fix for an error when there's a blank line in the configured patterns or excludes.
• #971: Fix for "exclude_from" files being completely ignored.
• #977: Fix for "exclude_patterns" and "exclude_from" not supporting explicit pattern styles (e.g.,
  "sh:" or "re:").

borgmatic 1.9.6

• #959: Fix an error in the Btrfs hook when a subvolume mounted at "/" is configured in borgmatic's
  source directories.
• #960: Fix for archives storing relative source directory paths such that they contain the working
  directory.
• #960: Fix the "spot" check to support relative source directory paths.
• #962: For the ZFS, Btrfs, and LVM hooks, perform path rewriting for excludes and patterns in
  addition to the existing source directories rewriting.
• #962: Under the hood, merge all configured source directories, excludes, and patterns into a
  unified temporary patterns file for passing to Borg. The borgmatic configuration options remain
  unchanged.
• #962: For the LVM hook, add support for nested logical volumes.
• #965: Fix a borgmatic runtime directory error when running the "spot" check with a database hook
  enabled.
• #969: Fix the "restore" action to work on database dumps without a port when a default port is
  present in configuration.
• Fix the "spot" check to no longer consider pipe files within an archive for file comparisons.
• Fix the "spot" check to have a nicer error when there are no source paths to compare.
• Fix auto-excluding of special files (when databases are configured) to support relative source
  directory paths.
• Drop support for Python 3.8, which has been end-of-lifed.

borgmatic 1.9.5

• #418: Backup and restore databases that have the same name but with different ports, hostnames,
  or hooks.
• #947: To avoid a hang in the database hooks, error and exit when the borgmatic runtime
  directory overlaps with the configured excludes.
• #954: Fix a findmnt command error in the Btrfs hook by switching to parsing JSON output.
• #956: Fix the printing of a color reset code even when color is disabled.
• #958: Drop colorama as a library dependency.
• When the ZFS, Btrfs, or LVM hooks aren't configured, don't try to cleanup snapshots for them.

borgmatic 1.9.4

• #80 (beta): Add an LVM hook for snapshotting and backing up LVM logical volumes. See the
  documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/snapshot-your-filesystems/
• #251 (beta): Add a Btrfs hook for snapshotting and backing up Btrfs subvolumes. See the
  documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/snapshot-your-filesystems/
• #926: Fix a library error when running within a PyInstaller bundle.
• #950: Fix a snapshot unmount error in the ZFS hook when using nested datasets.
• Update the ZFS hook to discover and snapshot ZFS datasets even if they are parent/grandparent
  directories of your source directories.
• Reorganize data source and monitoring hooks to make developing new hooks easier.

borgmatic 1.9.3

• #261 (beta): Add a ZFS hook for snapshotting and backing up ZFS datasets. See the documentation
  for more information: https://torsion.org/borgmatic/docs/how-to/snapshot-your-filesystems/
• Remove any temporary copies of the manifest file created in support of the "bootstrap" action.
• Deprecate the "store_config_files" option at the global scope and move it under the "bootstrap"
  hook. See the documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/extract-a-backup/#extract-the-configuration-files-used-to-create-an-archive
• Require the runtime directory to be an absolute path.
• Add a "--deleted" flag to the "repo-list" action for listing deleted archives that haven't
  yet been compacted (Borg 2 only).
• Promote the "spot" check from a beta feature to stable.

borgmatic 1.9.2

• #441: Apply the "umask" option to all relevant actions, not just some of them.
• #722: Remove the restriction that the "extract" and "mount" actions must match a single
  repository. Now they work more like other actions, where each repository is applied in turn.
• #932: Fix the missing build backend setting in pyproject.toml to allow Fedora builds.
• #934: Update the logic that probes for the borgmatic streaming database dump, bootstrap
  metadata, and check state directories to support more platforms and use cases. See the
  documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/backup-your-databases/#runtime-directory
• #934: Add the "RuntimeDirectory" and "StateDirectory" options to the sample systemd service
  file to support the new runtime and state directory logic.
• #939: Fix borgmatic ignoring the "BORG_RELOCATED_REPO_ACCESS_IS_OK" and
  "BORG_UNKNOWN_UNENCRYPTED_REPO_ACCESS_IS_OK" environment variables.
• Add a Pushover monitoring hook. See the documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#pushover-hook

borgmatic 1.9.1

• #928: Fix the user runtime directory location on macOS (and possibly Cygwin).
• #930: Fix an error with the sample systemd service when no credentials are configured.
• #931: Fix an error when implicitly upgrading the check state directory from ~/.borgmatic to
  ~/.local/state/borgmatic across filesystems.

borgmatic 1.9.0

• #609: Fix the glob expansion of "source_directories" values to respect the "working_directory"
  option.
• #609: BREAKING: Apply the "working_directory" option to all actions, not just "create". This
  includes repository paths, destination paths, mount points, etc.
• #562: Deprecate the "borgmatic_source_directory" option in favor of "user_runtime_directory"
  and "user_state_directory".
• #562: BREAKING: Move the default borgmatic streaming database dump and bootstrap metadata
  directory from ~/.borgmatic to /run/user/$UID/borgmatic, which is more XDG-compliant. You can
  override this location with the new "user_runtime_directory" option. Existing archives with
  database dumps at the old location are still restorable.
• #562, #638: Move the default check state directory from ~/.borgmatic to
  ~/.local/state/borgmatic. This is more XDG-compliant and also prevents these state files from
  getting backed up (unless you explicitly include them). You can override this location with the
  new "user_state_directory" option. After the first time you run the "check" action with borgmatic
  1.9.0, you can safely delete the ~/.borgmatic directory.
• #838: BREAKING: With Borg 1.4+, store database dumps and bootstrap metadata in a "/borgmatic"
  directory within a backup archive, so the path doesn't depend on the current user. This means
  that you can now backup as one user and restore or bootstrap as another user, among other use
  cases.
• #902: Add loading of encrypted systemd credentials. See the documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/provide-your-passwords/#using-systemd-service-credentials
• #911: Add a "key change-passphrase" action to change the passphrase protecting a repository key.
• #914: Fix a confusing apparent hang when when the repository location changes, and instead
  show a helpful error message.
• #915: BREAKING: Rename repository actions like "rcreate" to more explicit names like
  "repo-create" for compatibility with recent changes in Borg 2.0.0b10.
• #918: BREAKING: When databases are configured, don't auto-enable the "one_file_system" option,
  as existing auto-excludes of special files should be sufficient to prevent Borg from hanging on
  them. But if this change causes problems for you, you can always enable "one_file_system"
  explicitly.
• #919: Clarify the command-line help for the "--config" flag.
• #919: Document a policy for versioning and breaking changes:
  https://torsion.org/borgmatic/docs/how-to/upgrade/#versioning-and-breaking-changes
• #921: BREAKING: Change soft failure command hooks to skip only the current repository rather than
  all repositories in the configuration file.
• #922: Replace setup.py (Python packaging metadata) with the more modern pyproject.toml.
• When using Borg 2, default the "archive_name_format" option to just "{hostname}", as Borg 2 does
  not require unique archive names; identical archive names form a common "series" that can be
  targeted together. See the Borg 2 documentation for more information:
  https://borgbackup.readthedocs.io/en/2.0.0b13/changes.html#borg-1-2-x-1-4-x-to-borg-2-0
• Add support for Borg 2's "rclone:" repository URLs, so you can backup to 70+ cloud storage
  services whether or not they support Borg explicitly.
• Add support for Borg 2's "sftp://" repository URLs.
• Update the "--match-archives" and "--archive" flags to support Borg 2 series names or archive
  hashes.
• Add a "--match-archives" flag to the "prune" action.
• Add "--local-path" and "--remote-path" flags to the "config bootstrap" action for setting the
  Borg executable paths used for bootstrapping.
• Add a "--user-runtime-directory" flag to the "config bootstrap" action for helping borgmatic
  locate the bootstrap metadata stored in an archive.
• Add a Zabbix monitoring hook. See the documentation for more information:
  https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#zabbix-hook
• Add a tarball of borgmatic's HTML documentation to the packages on the project page.

borgmatic 1.8.14

• #896: Fix an error in borgmatic rcreate/init on an empty repository directory with Borg 1.4.
• #898: Add glob ("*") support to the "--repository" flag. Just quote any values containing
  globs so your shell doesn't interpret them.
• #899: Fix for a "bad character" Borg error in which the "spot" check fed Borg an invalid pattern.
• #900: Fix for a potential traceback (TypeError) during the handling of another error.
• #904: Clarify the configuration reference about the "spot" check options:
  https://torsion.org/borgmatic/docs/reference/configuration/
• #905: Fix the "source_directories_must_exist" option to work with relative "source_directories"
  paths when a "working_directory" is set.
• #906: Add documentation details for how to run custom database dump commands using binaries from
  running containers:
  https://torsion.org/borgmatic/docs/how-to/backup-your-databases/#containers
• Fix a regression in which the "color" option had no effect.
• Add a recent contributors section to the documentation, because credit where credit's due! See:
  https://torsion.org/borgmatic/#recent-contributors