You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is_mcq_subject_qnode() in trapi.py made more tolerant of set_interpretation annotation on secondary query nodes. Release 0.1.0 also has partial implementation (incomplete) supporting a Docker Compose managed local semsim server (but keeps the default mode as external Monarch API semsimian calls for now).
Copy file name to clipboardexpand all lines: CHANGELOG.md
+5
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,10 @@
1
1
# Change Log
2
2
3
+
## 0.1.0
4
+
5
+
- Constraints relaxed for the filtering of Query Node specification of set_interpretation such that incomplete nodes (which may be specified as a part of multistep MCQ) generate a warning but are ignored (they don't now raise an exception).
6
+
- minor release includes partial implementation (including SEMSIMIAN related environment variables, including a new SEMSIMIAN_MODE flag to tag two distinct layers of SemSimian access: server and (indirect) Monarch)
7
+
3
8
## 0.0.12
4
9
5
10
- Input Query Graph list of nodes more robustly checked for constrain of having one and only one well-formed MCQ node with a set_interpretation directive
Copy file name to clipboardexpand all lines: DEVELOPER_README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -24,11 +24,11 @@ Steps to properly issue a new project release:
24
24
25
25
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)
26
26
2. Document release changes in the **CHANGELOG.md**
27
-
3. Update the **`[Tool Poetry]version =`** field in the **pyprojects.yaml**, e.g. "0.0.12"
27
+
3. Update the **`[Tool Poetry]version =`** field in the **pyprojects.yaml**, e.g. "0.1.0"
28
28
4. Run **`poetry update`** (preferably, within a **`poetry shell`**)
29
29
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.
30
30
6. Commit or pull request merge all files (including the **poetry.lock** file) to the local **main** branch.
31
-
7. Add the equivalent Git **tag** to **main**. This should be the Semantic Version string from step 4 with an added 'v' prefix, e.g. "v0.0.9".
31
+
7. Add the equivalent Git **tag** to **main**. This should be the Semantic Version string from step 4 with an added 'v' prefix, e.g. "v0.1.0".
32
32
8. Push **main** to remote.
33
33
9. Check if Git Actions for testing and documentation complete successfully.
34
34
10. Create a Git package release using the same release tag, e.g. "v0.0.9".
0 commit comments