build: Version 4.0.0

.bumpversion.cfg

@@ -2,7 +2,7 @@
 commit = True
 tag = True
 message = build: Version {new_version}
-current_version = 3.3.0
+current_version = 4.0.0
 
 [bumpversion:file:CHANGELOG.md]
 search = Unreleased

CHANGELOG.md

@@ -1,4 +1,4 @@
-## Unreleased
+## Version 4.0.0 (2024-10-07)
 
 * [Enhancement] Drop support for Python 3.8; update the Ubuntu base image to
   "Ubuntu Jammy" (22.04).

README.md

@@ -48,7 +48,7 @@ appropriate one:
 
 ## Installation
 
-    pip install git+https://github.com/hastexo/tutor-contrib-backup@v3.3.0
+    pip install git+https://github.com/hastexo/tutor-contrib-backup@v4.0.0
 
 ## Usage
 
@@ -71,7 +71,7 @@ You can do this in one of two ways:
    In this case, this plugin will push the `backup` image to your previously configured registry.
 2. You override just the `BACKUP_DOCKER_IMAGE` configuration value, for example:
    ```
-   tutor config save --set BACKUP_DOCKER_IMAGE=localhost:5000/backup:v3.3.0
+   tutor config save --set BACKUP_DOCKER_IMAGE=localhost:5000/backup:v4.0.0
    ```
    Substitute the correct registry prefix if, rather than using a local instance of the [Distribution Registry](https://github.com/distribution/distribution), you are using a container registry provided by [GitHub](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry), [GitLab](https://docs.gitlab.com/ee/user/packages/container_registry/), [Harbor](https://goharbor.io/), etc.
 
@@ -203,7 +203,7 @@ This prevents your users from encountering errors during the restore process.
 
 ### General options
 
-* `BACKUP_DOCKER_IMAGE` (default: `<DOCKER_REGISTRY>backup:v3.3.0`, relative to `DOCKER_REGISTRY` as defined by the global Tutor option)
+* `BACKUP_DOCKER_IMAGE` (default: `<DOCKER_REGISTRY>backup:v4.0.0`, relative to `DOCKER_REGISTRY` as defined by the global Tutor option)
 
 ### Kubernetes options