Skip to content

0.6.3

Choose a tag to compare

@cursor cursor released this 24 Sep 10:37
· 167 commits to development since this release
06e8ead

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 --strict

Fixed

  • A missing tip SHA names CI_COMMIT_SHA, GITHUB_SHA, or BUILD_SOURCEVERSION instead of 'NoneType' object has no attribute 'encode' (#339).
  • Azure STAGING without SYSTEM_PULLREQUEST_SOURCEBRANCH and SYSTEM_PULLREQUEST_TARGETBRANCHNAME names those variables. The check runs before origin.fetch(), so a checkout with no remote no longer dies with No git repository was found at origin (#339).
  • A GitHub or Azure pull-request ref that is not on origin reports Could not find git ref origin/<name> instead of Invalid object name (#339).
  • DEBUG, MANUAL, and ALWAYS under CI report Deployment plan <NAME> is not a CI diff plan. Use STAGING, PRODUCTION, or FULL. ALWAYS is no longer an alias of FULL (#339).
  • A GitLab merged-result commit with one parent keeps CI_COMMIT_SHA and exits 0 when both SHAs are in the checkout, instead of list 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 --strict

Expect 0.6.3.

Links

License: EUPL-1.2. Issues: OpenTideHQ/opentide.