Repository navigation
0.6.1
0.6.1 — CI deploy plans, setup path, and promotion flags
23 September 2026. Patch on 0.6.0.
Upgrade if a CI STAGING or PRODUCTION plan skipped a changed rule file that sits directly in objects/rules/: 0.6.0 left that file out of the plan, and 0.6.1 deploys it. A file in a subdirectory of objects/rules/ is still not deployed. The missing-checkout failure is still exit 1, with a different message.
Install
pip install opentide==0.6.1
export OPENTIDE_REPO_ROOT=/path/to/detection-repo
opentide validate --strictChanged
- CI
STAGINGandPRODUCTIONplans include a changed rule file that sits directly inobjects/rules/. 0.6.0 matched the git diff against an absolute rules path, so a repo-relative entry such asobjects/rules/rule.yamlwas left out (#318).
Fixed
deploy --plan STAGINGorPRODUCTIONoutside a git checkout names the directory it searched and points at--plan FULL, instead ofNo git repository was found at None.FULLstill does not need a checkout (#310).opentide setup --path .from a subdirectory of a git checkout scaffolds that directory. An explicit--repostill replaces.(#324).opentide setup --no-promotionand--promotion-targetwrite[promotion]without--ci(#325).
Verify
python -c "import opentide; print(opentide.__version__)"
opentide setup --yes --name "Tutorial Detections" --org "Example Corp" --platform sentinel --path /tmp/tutorial-detections
opentide --repo /tmp/tutorial-detections validate --strictExpect 0.6.1.
Links
- PyPI
- GitHub Release
- CHANGELOG
- Usage → Releases
- Tracking issue: #328
License: EUPL-1.2. Issues: OpenTideHQ/opentide.