Preparing for release v4.1.4

CHANGELOG.md

@@ -4,8 +4,10 @@ The Reasoner Validator package is evolving along with progress in TRAPI and Biol
 
 ## 4.1.4
 
-- Added more fine-grained validation reporting inside case_input_found_in_response() TRAPI Response validation method, also injecting externalized "missing edge" validation message into method(); added/refactored validation codes accordingly
-- Full TRAPI 1.5.0 unit tests still skipped (need rework)
+- cleaned up predicate mixin handling distinguishing between Biolink Model 4.2.0 versus pre-4.2.0 validation.
+- Added more fine-grained validation reporting inside case_input_found_in_response() TRAPI Response validation method, also extracted "missing edge" validation message from graph-validation-tests module and embedded it into method(); added/refactored validation codes accordingly
+- Full TRAPI 1.5.0 unit tests still skipped (need rework); some other unit test temporarily skipped (due to TRAPI master branch schema bugs).
+- git action updates
 
 ## 4.1.3
 

DEVELOPER_NOTES.md

@@ -25,7 +25,7 @@ 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. 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.
+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.4"