chore: Automate setting of X.Y.Z to new version number in release

Author: claremacrae

contributing/Documentation/Version numbers in documentation.md

@@ -23,3 +23,5 @@ This placeholder is used when you need to tag a sub-part of something, for examp
 
 > [!Tip]
 > We have Templater templates for both these blocks. Use the `<%` icon in the Ribbon choose a template and insert it where the cursor is.
+
+The [release.sh](https://github.com/obsidian-tasks-group/obsidian-tasks/blob/main/release.sh) script automatically updates all `X.Y.Z` to the new version number during the release.

contributing/Releases/How do I make a release.md

@@ -8,7 +8,6 @@
     - Backwards incompatible change: increase major version
     - New functionality: increase minor version
     - Only bug fixes: increase patch version
-1. Having decided on the new version, replace all `X.Y.Z` in the documentation with the new version number.
 1. Check the current version of the obsidian dependency in [package.json](https://github.com/obsidian-tasks-group/obsidian-tasks/blob/main/package.json) (for example, `0.13.21`)
 1. Run `./release.sh <new tasks version> <obsidian version>`
     - Make sure there are no uncommitted changes. Stash them if necessary.

release.sh

@@ -30,6 +30,9 @@ read -p "Continue? [y/N] " -n 1 -r
 echo
 if [[ $REPLY =~ ^[Yy]$ ]]
 then
+  echo "Updating X.Y.Z version numbers in docs"
+  find ./docs/ -name _meta -prune -o -type f -name '*.md' -exec sed -i '' s/X\.Y\.Z/${NEW_VERSION}/g {} +
+
   echo "Updating package.json"
   TEMP_FILE=$(mktemp)
   jq ".version |= \"${NEW_VERSION}\"" package.json > "$TEMP_FILE" || exit 1