Preparing for minor patch release 3.8.9

DEVELOPER_NOTES.md

@@ -24,14 +24,15 @@ For Github-related performance reasons, as of project release v3.8.3, the code c
 
 Steps to properly issue a new project release:
 
-1. Perform any required **codes.yaml** and TRAPI **versions.yaml** updates (as above)
-2. Run the unit test suite to ensure that nothing fails. Iterate to fix failures (in the code or in terms of revised unit tests to reflect fresh code designs)
-3. Document release changes in the **CHANGELOG.md**
-4. Update the **`[Tool Poetry]version =`** field in the **pyprojects.yaml**, e.g. "3.8.8"
-5. Run **`poetry update`** (preferably within  **`poetry shell`**)
-6. Commit or pull request merge all files (including the **poetry.lock** file) to **master**
-7. Add the equivalent Git **tag** to **master**. This should be the Semantic Version string from step 4 with an added 'v' prefix, i.e. "v3.8.3".
-8. Push **master** to remote (if not already done with by a pull request in step 6).
-9. Check if Git Actions for testing and documentation complete successfully.
-10. Create the release using the same release tag, i.e. "v3.8.3".
-11. Check if Git Action for package deployment is successful and check if the new version (i.e. "3.8.3") is now visible on **[pypy.org](https://pypi.org/search/?q=reasoner-validator)**
+1. Perform any required **codes.yaml** and TRAPI **versions.yaml** updates (as above). 
+2. If the codes.yaml were revised, regenerated the associate code documentation by running the reasoner_validator/validation_codes.py module as a script from t he CLI.
+3. Run the unit test suite to ensure that nothing fails. Iterate to fix failures (in the code or in terms of revised unit tests to reflect fresh code designs)
+4. Document release changes in the **CHANGELOG.md**
+5. Update the **`[Tool Poetry]version =`** field in the **pyprojects.yaml**, e.g. "3.8.9"
+6. Run **`poetry update`** (preferably within  **`poetry shell`**)
+7. Commit or pull request merge all files (including the **poetry.lock** file) to **master**
+8. Add the equivalent Git **tag** to **master**. This should be the Semantic Version string from step 4 with an added 'v' prefix, i.e. "v3.8.3".
+9. Push **master** to remote (if not already done with by a pull request in step 6).
+10.  Check if Git Actions for testing and documentation complete successfully.
+11. Create the release using the same release tag, i.e. "v3.8.3".
+12. Check if Git Action for package deployment is successful and check if the new version (i.e. "3.8.3") is now visible on **[pypy.org](https://pypi.org/search/?q=reasoner-validator)**

pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "reasoner-validator"
-version = "3.8.8"
+version = "3.8.9"
 description = "Validation tools for Reasoner API"
 authors = [
     "Richard Bruskiewich <richard.bruskiewich@delphinai.com>",