- The sientia-module entrypoint now merges requirements.txt with the
Plugin Store runtime and installs both before boot (SIENTIAPDE-2223),
so the worker no longer calls install_runtime or runs the loaded
package version guard.
- Leave runtime libs unpinned in requirements files so the runtime
version wins; cap sqlalchemy<2.1 and evidently<0.7 for compatibility.
- Update README, CLAUDE.md and worker tests to match.
The probes only check app_up, which was set to 1 when the metrics server started,
before install_runtime. A pod that would fail the guard could turn Ready first, so a
rollout would remove the old pod. app_up now goes to 1 right after the guard.
Also: copy sys.modules keys before iterating, raise the sientia_model floor to the
runtime's >=0.14.0, pin the same runtime versions in requirements-local.txt, test
that the snapshot is taken before the install and the real importlib.metadata path,
and document the boot failure in README and CLAUDE.md.
Picks up the notification timestamp -> native datetime fix; also
aligns requirements.txt's floor with requirements-local.txt's pin
(was >=1.11.0/@1.12.0, out of sync with the other repos).
- Updated `sientia-dataops-library` to version 1.12.0 and `sientia-model-library` to version 0.8.3 in `requirements-local.txt` for improved features and compatibility.
- Changed `sientia_do` and `sientia_model` in `requirements.txt` to use version specifiers for better flexibility in dependency management.
- Upgraded sientia-model-library from version 0.7.4 to 0.7.5 in both requirements-local.txt and requirements.txt.
- Modified quality-gate.yml to include sientia-model-library in the repositories list for improved CI/CD integration.
