diff --git a/CITATION.cff b/CITATION.cff
index 6c1f9dd7..df1f7a49 100644
--- a/CITATION.cff
+++ b/CITATION.cff
@@ -42,9 +42,9 @@ authors:
     given-names: Haris
     orcid: "https://orcid.org/0000-0001-6975-5960"
 cff-version: "1.1.0"
-date-released: 2022-02-24
+date-released: 2023-08-04
 message: "If you use hazen in your work, please cite it using these metadata."
 repository-code: "https://github.com/GSTT-CSC/hazen"
 title: hazen
-version: "1.2.0"
+version: "1.3.0"
 ...
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0c19d760..b0ecaca9 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -101,7 +101,7 @@ For a new release: <br>
 5. **Important**: Update version numbers across the repo:
    - Update version number in `hazenlib/_version.py`
      - This is automatically propagated into `docs/source/conf.py`, `hazenlib/__init__.py` and `setup.cfg`
-   - Update version number in `CITATION.cff`
+   - Update version number and date released in `CITATION.cff`
 6. Create a [new Release](https://github.com/GSTT-CSC/hazen/releases)
    - Create a tag equal to the version number, e.g. 1.2.1
    - Select `main` as the Target branch from which to create the Release
diff --git a/hazenlib/_version.py b/hazenlib/_version.py
index 58d478ab..19b4f1d6 100644
--- a/hazenlib/_version.py
+++ b/hazenlib/_version.py
@@ -1 +1 @@
-__version__ = '1.2.0'
+__version__ = '1.3.0'