Repository navigation
0.6.3
0.6.3 — Remaining CI diff failures
24 September 2026. Patch on 0.6.2.
Upgrade if a CI diff plan still crashed after 0.6.2 with encode, KeyError, Invalid object name, or list index out of range. Each of those cases still exits 1, with a sentence instead of the exception. FULL is unchanged.
Install
pip install opentide==0.6.3
export OPENTIDE_REPO_ROOT=/path/to/detection-repo
opentide validate --strictFixed
- A missing tip SHA names
CI_COMMIT_SHA,GITHUB_SHA, orBUILD_SOURCEVERSIONinstead of'NoneType' object has no attribute 'encode'(#339). - Azure
STAGINGwithoutSYSTEM_PULLREQUEST_SOURCEBRANCHandSYSTEM_PULLREQUEST_TARGETBRANCHNAMEnames those variables. The check runs beforeorigin.fetch(), so a checkout with no remote no longer dies withNo git repository was found at origin(#339). - A GitHub or Azure pull-request ref that is not on
originreportsCould not find git ref origin/<name>instead ofInvalid object name(#339). DEBUG,MANUAL, andALWAYSunder CI reportDeployment plan <NAME> is not a CI diff plan. Use STAGING, PRODUCTION, or FULL.ALWAYSis no longer an alias ofFULL(#339).- A GitLab merged-result commit with one parent keeps
CI_COMMIT_SHAand exits0when both SHAs are in the checkout, instead oflist index out of range(#339).
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.3.
Links
- PyPI
- GitHub Release
- CHANGELOG
- Usage → Releases
- Tracking issue: #343
License: EUPL-1.2. Issues: OpenTideHQ/opentide.