preparing for v0.0.11 patch release

Author: RichardBruskiewich

CHANGELOG.md

@@ -1,5 +1,10 @@
 # Change Log
 
+## 0.0.11
+
+- added new 'test.yml' workflow for CI validation of commits to the main branch
+- removed 'is_set' expectation from QNode validation of MCQ inputs since 'set_interpretation' only is now used
+
 ## 0.0.10
 
 - added "directionality": "object_to_subject" to SemSimian API call (as per recommendation of MMCQ team)

DEVELOPER_README.md

@@ -24,7 +24,7 @@ Steps to properly issue a new project release:
 
 1. 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)
 2. Document release changes in the **CHANGELOG.md**
-3. Update the **`[Tool Poetry]version =`** field in the **pyprojects.yaml**, e.g. "0.0.10"
+3. Update the **`[Tool Poetry]version =`** field in the **pyprojects.yaml**, e.g. "0.0.11"
 4. Run **`poetry update`** (preferably, within a **`poetry shell`**)
 5. 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.
 6. Commit or pull request merge all files (including the **poetry.lock** file) to the local **main** branch.

poetry.lock

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "monarch-trapi-kp"
-version = "0.0.10"
+version = "0.0.11"
 description = "Translator (Knowledge Provider) Reasoner API wrapper for the Semantic Similarity algorithm against the knowledge graph of the Monarch Initiative information system"
 authors = [
     "Richard Bruskiewich <richard.bruskiewich@delphinai.com>",