Check that the Change Log contains the new version when releasing

Author: Clément Le Provost

release.sh

@@ -28,11 +28,22 @@ fi
 VERSION_CODE=$1
 
 # Check that the working repository is clean (without any changes, neither staged nor unstaged).
-if [[ ! -z `git status --porcelain` ]]; then
+# An exception is the change log, which should have been edited, but not necessarily committed (we usually commit it
+# along with the version number).
+if [[ ! -z `git status --porcelain | grep -v "ChangeLog.md"` ]]; then
     echo "ERROR: Working copy not clean! Aborting." 1>&2
     echo "Please revert or commit any pending changes before releasing." 1>&2
     exit 1
-fi 
+fi
+
+# Check that the change log contains information for the new version.
+set +e
+version_in_change_log=$(cat "$SELF_ROOT/ChangeLog.md" | grep -E "^#+" | sed -E 's/^#* ([0-9.]*)\s*.*$/\1/g' | grep -x "$VERSION_CODE")
+set -e
+if [[ -z $version_in_change_log ]]; then
+    echo "Version $VERSION_CODE not found in change log! Aborting." 1>&2
+    exit 2
+fi
 
 $SELF_ROOT/tools/update-version.sh $VERSION_CODE