Repository navigation
0.6.2
0.6.2 — GitLab base commit and GitHub pull-request refs
24 September 2026. Patch on 0.6.1.
Upgrade if a GitLab STAGING or PRODUCTION plan crashed with 'Repo' object has no attribute 'lookup_ref', or a GitHub STAGING plan asked for Azure pull-request variables and then KeyError. Both still exit 1. GitLab reports No Source Commit Found. GitHub names GITHUB_HEAD_REF and GITHUB_BASE_REF.
Install
pip install opentide==0.6.2
export OPENTIDE_REPO_ROOT=/path/to/detection-repo
opentide validate --strictFixed
- GitLab
STAGINGandPRODUCTIONwith an unset or unknown base SHA exit1withNo Source Commit Foundinstead ofFATAL: 'Repo' object has no attribute 'lookup_ref'. The same command still succeeds when both SHAs are in the checkout (#333). - GitHub Actions
STAGINGwithoutGITHUB_HEAD_REFandGITHUB_BASE_REFexits1withExpected to find GITHUB_HEAD_REF and GITHUB_BASE_REF | Ensure this is running in a Pull Request pipeline. 0.6.1 asked for AzureSYSTEM_PULLREQUEST_SOURCEBRANCHandSYSTEM_PULLREQUEST_TARGETBRANCHNAME, thenKeyError while compiling the deployment plan(#334).
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.2.
Links
- PyPI
- GitHub Release
- CHANGELOG
- Usage → Releases
- Tracking issue: #337
License: EUPL-1.2. Issues: OpenTideHQ/opentide.