Preparing for release v4.1.8

CHANGELOG.md

@@ -2,6 +2,11 @@
 
 The Reasoner Validator package is evolving along with progress in TRAPI and Biolink Model standards within the NCATS Biomedical Knowledge Translator.
 
+## 4.1.8
+
+- BMT update to 1.4.1 (with default Biolink Model 4.2.1)
+- implemented rudimentary **`biolink:treats`** predicate validation check for **`biolink:supporting_graph`** attribute value.
+
 ## 4.1.7
 
 - Fixed mixin predicates to be allowed in both Query Graph and Knowledge Graph contexts; however, this may be overridden by explicitly setting strict_validation to true

DEVELOPER_NOTES.md

@@ -28,12 +28,12 @@ Steps to properly issue a new project release:
 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 the 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. "4.1.7"
+5. Update the **`[Tool Poetry]version =`** field in the **pyprojects.yaml**, e.g. "4.1.8"
 6. Run **`poetry update`** (preferably within  **`poetry shell`**)
 7. The project pip **requirements.txt** file snapshot of dependencies should also be updated at this point (type **`$ poetry export --output requirements.txt`**, assuming that the [proper poetry export plugin is installed](https://python-poetry.org/docs/pre-commit-hooks#poetry-export)). This may facilitate module deployment within environments that prefer to use pip rather than poetry to manage their deployments. 
 8. Commit or pull request merge all files (including the **poetry.lock** file) to **master**
-9. Add the equivalent Git **tag** to **master**. This should be the Semantic Version string from step 4 with an added 'v' prefix, i.e. "v4.1.7". 
+9. Add the equivalent Git **tag** to **master**. This should be the Semantic Version string from step 4 with an added 'v' prefix, i.e. "v4.1.8". 
 10. Push **master** to remote.
 11. Check if Git Actions for testing and documentation complete successfully.
-12. Create the release using the same release tag, i.e. "v4.1.7". 
-13. Check if Git Action for package deployment is successful and check if the new version (i.e. "4.1.7") is now visible on **[pypy.org](https://pypi.org/search/?q=reasoner-validator)**
+12. Create the release using the same release tag, i.e. "v4.1.8". 
+13. Check if Git Action for package deployment is successful and check if the new version (i.e. "4.1.8") 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 = "4.1.7"
+version = "4.1.8"
 description = "Validation tools for Reasoner API"
 authors = [
     "Richard Bruskiewich <richard.bruskiewich@delphinai.com>",