Change borgmatic 1.8.15 (unreleased) to 1.9.0 due to breaking changes.

NEWS

@@ -1,4 +1,4 @@
-1.8.15.dev0
+1.9.0.dev0
  * #914: Fix a confusing apparent hang when when the repository location changes, and instead
    show a helpful error message.
  * #919: Clarify the command-line help for the "--config" flag.
@@ -9,8 +9,8 @@
    them. But if this change causes problems for you, you can always enable "one_file_system"
    explicitly.
  * #911: Add a "key change-passphrase" action to change the passphrase protecting a repository key.
- * #915: Rename repository actions like "rcreate" to more explicit names like "repo-create" for
-   compatibility with recent changes in Borg 2.0.0b10.
+ * #915: BREAKING: Rename repository actions like "rcreate" to more explicit names like
+   "repo-create" for compatibility with recent changes in Borg 2.0.0b10.
 
 1.8.14
  * #896: Fix an error in borgmatic rcreate/init on an empty repository directory with Borg 1.4.

docs/how-to/backup-your-databases.md

@@ -466,13 +466,13 @@ exclude them. <span class="minilink minilink-addedin">Prior to version
 1.7.3</span>Special files were not auto-excluded, and you were responsible for
 excluding them yourself. Common directories to exclude are `/dev` and `/run`,
 but that may not be exhaustive.
-5. <span class="minilink minilink-addedin">Prior to version 1.8.15</span>
+5. <span class="minilink minilink-addedin">Prior to version 1.9.0</span>
 Database hooks also implicitly enabled the `one_file_system` option, which
 meant Borg wouldn't cross filesystem boundaries when looking for files to
 backup. When borgmatic was running in a container, this often required a
 work-around to explicitly add each mounted backup volume to
 `source_directories` instead of relying on Borg to include them implicitly via
-a parent directory. But as of borgmatic 1.8.15, `one_file_system` is no longer
+a parent directory. But as of borgmatic 1.9.0, `one_file_system` is no longer
 auto-enabled and such work-arounds aren't necessary.
 
 

docs/how-to/inspect-your-backups.md

@@ -62,7 +62,7 @@ for available values.
 
 (No borgmatic `list` or `info` actions? Upgrade borgmatic!)
 
-<span class="minilink minilink-addedin">New in borgmatic version 1.8.15</span>
+<span class="minilink minilink-addedin">New in borgmatic version 1.9.0</span>
 There are also `repo-list` and `repo-info` actions for displaying repository
 information with Borg 2.x:
 

docs/how-to/set-up-backups.md

@@ -214,7 +214,7 @@ command like the following with Borg 1.x:
 sudo borgmatic init --encryption repokey
 ```
 
-<span class="minilink minilink-addedin">New in borgmatic version 1.8.15</span>
+<span class="minilink minilink-addedin">New in borgmatic version 1.9.0</span>
 Or, with Borg 2.x:
 
 ```bash

docs/how-to/upgrade.md

@@ -92,7 +92,7 @@ versioning. But here's how borgmatic versioning generally works:
  * Minor version bumps (e.g., 1.8 to 1.9): Medium breaking changes. Depending
    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.14 to 1.8.15): Minor breaking changes. These
+ * 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.
 
@@ -112,7 +112,7 @@ Borg releases require additional steps that borgmatic can help with.
 
 ### Borg 1.2 to 2.0
 
-<span class="minilink minilink-addedin">New in borgmatic version 1.8.15</span>
+<span class="minilink minilink-addedin">New in borgmatic version 1.9.0</span>
 Upgrading Borg from 1.2 to 2.0 requires manually upgrading your existing Borg
 1 repositories before use with Borg or borgmatic. Here's how you can
 accomplish that.

setup.py

@@ -1,6 +1,6 @@
 from setuptools import find_packages, setup
 
-VERSION = '1.8.15.dev0'
+VERSION = '1.9.0.dev0'
 
 
 setup(