diff --git a/NEWS b/NEWS index 700c1cdc..f739a501 100644 --- a/NEWS +++ b/NEWS @@ -1,4 +1,4 @@ -1.9.0.dev0 +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 @@ -6,17 +6,18 @@ * #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. Override - this location with the new "user_runtime_directory" option. Existing archives with database dumps - at the old location are still restorable. + 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). Override this location with the new - "user_state_directory" option. After the first time you run the "check" action with borgmatic + 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: 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. + * #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 * #914: Fix a confusing apparent hang when when the repository location changes, and instead @@ -37,7 +38,7 @@ * 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.0b12/changes.html#borg-1-2-x-1-4-x-to-borg-2-0 + 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. diff --git a/docs/how-to/make-per-application-backups.md b/docs/how-to/make-per-application-backups.md index afc7e875..095fef5f 100644 --- a/docs/how-to/make-per-application-backups.md +++ b/docs/how-to/make-per-application-backups.md @@ -141,7 +141,7 @@ for more information. With Borg version 2.xSee the [match archives -documentation](https://borgbackup.readthedocs.io/en/2.0.0b12/usage/help.html#borg-help-match-archives). +documentation](https://borgbackup.readthedocs.io/en/2.0.0b13/usage/help.html#borg-help-match-archives). Some borgmatic command-line actions also have a `--match-archives` flag that overrides both the auto-matching behavior and the `match_archives` diff --git a/docs/how-to/upgrade.md b/docs/how-to/upgrade.md index cf75124c..8d34d5d3 100644 --- a/docs/how-to/upgrade.md +++ b/docs/how-to/upgrade.md @@ -93,8 +93,8 @@ versioning. But here's how borgmatic versioning generally works: on the features you use, this may be a drop-in replacement. But read the release notes to make sure. * Patch version bumps (e.g., 1.8.13 to 1.8.14): Minor breaking changes. These - include, for instance, bug fixes that are technically breaking and may only - affects a small subset of users. + include, for instance, bug fixes that are technically breaking but may only + affect a small subset of users. Each breaking change is prefixed with "BREAKING:" in [borgmatic's release notes](https://projects.torsion.org/borgmatic-collective/borgmatic/releases), @@ -193,7 +193,7 @@ confirmation of success—or tells you if something hasn't been transferred yet. Note that by omitting the `--upgrader` flag, you can also do archive transfers between related Borg 2 repositories without upgrading, even down to individual archives. For more on that functionality, see the [Borg transfer -documentation](https://borgbackup.readthedocs.io/en/2.0.0b12/usage/transfer.html). +documentation](https://borgbackup.readthedocs.io/en/2.0.0b13/usage/transfer.html). That's it! Now you can use your new Borg 2 repository as normal with borgmatic. If you've got multiple repositories, repeat the above process for diff --git a/pyproject.toml b/pyproject.toml index 978a484d..647fa06a 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,6 +1,6 @@ [project] name = "borgmatic" -version = "1.9.0.dev0" +version = "1.9.0" authors = [ { name="Dan Helfman", email="witten@torsion.org" }, ]