diff --git a/CHANGELOG.md b/CHANGELOG.md
index 309e859d7..c16e4bad2 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,7 +2,7 @@ Unlike the Git commit history, this changelog does not include code cleanups
 and other details that don't affect using Porcupine.
 
 
-## Unreleased
+## v2022.07.31
 
 Porcupine now uses [calver](https://calver.org/):
 from now on, a Porcupine version is simply its release date in the "year.month.day" format.
diff --git a/README.md b/README.md
index 707b72602..77780b8d7 100644
--- a/README.md
+++ b/README.md
@@ -260,7 +260,7 @@ Other people shouldn't need them.
     changing the changelog afterwards is difficult, as the text gets copied into the releases page.
 3. Merge the pull request and pull the merge commit to your local `master` branch.
 4. Run `python3 scripts/release.py` from the `master` branch.
-    The script pushes a tag named e.g. `v2022.07.29`,
+    The script pushes a tag named e.g. `v2022.07.31`,
     which triggers the parts of `.github/workflows/build.yml`
     that have `if: startsWith(github.ref, 'refs/tags/v')` in them.
     They build and deploy docs, copy the changelog to the releases page, and so on.
diff --git a/porcupine/__init__.py b/porcupine/__init__.py
index d281ba4d2..97646e785 100644
--- a/porcupine/__init__.py
+++ b/porcupine/__init__.py
@@ -11,7 +11,7 @@
 
 import appdirs
 
-version_info = (2022, 7, 29)  # this is updated with scripts/release.py
+version_info = (2022, 7, 31)  # this is updated with scripts/release.py
 __version__ = "%d.%02d.%02d" % version_info
 __author__ = "Akuli"
 __copyright__ = "Copyright (c) 2017-2022 Akuli"