diff --git a/CHANGELOG.md b/CHANGELOG.md
index 971c09914..647e64a36 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -11,6 +11,10 @@ A raw git diff can be seen [here][unreleased].
 
 <!--next-->
 
+## [5.1.3] 2022-07-21
+
+-   [#1229](https://github.com/SMI/SmiServices/pull/1229) by dependabot. Bump IsIdentifiable from 0.0.4 to 0.0.5 to fix broken API
+
 ## [5.1.2] 2022-07-18
 
 ## Bugfix
@@ -1112,7 +1116,8 @@ First stable release after importing the repository from the private
 -   Anonymous `MappingTableName` must now be fully specified to pass validation
     (e.g. `mydb.mytbl`). Previously skipping database portion was supported.
 
-[unreleased]: https://github.com/SMI/SmiServices/compare/v5.1.2...master
+[unreleased]: https://github.com/SMI/SmiServices/compare/v5.1.3...master
+[5.1.3]: https://github.com/SMI/SmiServices/compare/v5.1.2...v5.1.3
 [5.1.2]: https://github.com/SMI/SmiServices/compare/v5.1.1...v5.1.2
 [5.1.1]: https://github.com/SMI/SmiServices/compare/v5.1.0...v5.1.1
 [5.1.0]: https://github.com/SMI/SmiServices/compare/v5.0.1...v5.1.0
diff --git a/README.md b/README.md
index 25053326b..2eaa60ce2 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@
 ![GitHub](https://img.shields.io/github/license/SMI/SmiServices)
 [![Total alerts](https://img.shields.io/lgtm/alerts/g/SMI/SmiServices.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/SMI/SmiServices/alerts/)
 
-Version: `5.1.2`
+Version: `5.1.3`
 
 # SMI Services
 
diff --git a/docs/RELEASING.md b/docs/RELEASING.md
index cb8ebbfc2..e4b2abf67 100644
--- a/docs/RELEASING.md
+++ b/docs/RELEASING.md
@@ -36,7 +36,7 @@ The release workflow is to checkout a new `release/` branch from master, update
     Switched to a new branch 'release/v1.2.3'
     ```
 
--   Update the [CHANGELOG](/CHANGELOG.md) for the new release. This involves running the `bin/release/updateChangelog.py` script. Review the diff and check for any obvious errors.
+-   Update the [CHANGELOG](/CHANGELOG.md) for the new release. This involves running `./bin/release/updateChangelog.py <prev version> <next version>`. Note that this currently requires `prettier` to be installed from npm. Review the diff and check for any obvious errors.
 
 -   Update any other files referencing the version. To see an example, check the previous release PR. At time of writing, these are:
     -   `README.md`: Bump the version in the header
diff --git a/src/SharedAssemblyInfo.cs b/src/SharedAssemblyInfo.cs
index dd48de451..504dbe33a 100644
--- a/src/SharedAssemblyInfo.cs
+++ b/src/SharedAssemblyInfo.cs
@@ -7,6 +7,6 @@
 [assembly: AssemblyCulture("")]
 
 // These should be overwritten by release builds
-[assembly: AssemblyVersion("5.1.1")]
-[assembly: AssemblyFileVersion("5.1.2")]
-[assembly: AssemblyInformationalVersion("5.1.2")] // This one can have the extra build info after it
+[assembly: AssemblyVersion("5.1.3")]
+[assembly: AssemblyFileVersion("5.1.3")]
+[assembly: AssemblyInformationalVersion("5.1.3")] // This one can have the extra build info after it