Skip to content

0.7.0

Choose a tag to compare

View all tags
@cursor cursor released this 29 Sep 03:01
· 120 commits to development since this release
v0.7.0
aee48c7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

0.7.0 — Share Tide objects to MISP

29 September 2026. Minor on 0.6.4.

Upgrade to publish threats, objectives, and rules to MISP, or regenerate CI so a GitHub production job compares github.ref to a literal ref. The share stage stays off until you pass --sharing.

Install

pip install opentide==0.7.0
export OPENTIDE_REPO_ROOT=/path/to/detection-repo
opentide validate --strict

Regenerate an existing workflow with opentide setup ci <github|gitlab|azure> --yes. Add --sharing when that pipeline should share changed objects on the default branch.

Added

  • opentide share publishes one Tide object as one MISP Event. Commands: push, preview, status, retract, targets. preview and status make no request. The API key is never printed (#184, #371, #372).
  • .opentide/configurations/sharing.toml merges [[misp]] blocks by name (#370).
  • Successful shares are recorded in .opentide/states/sharing.jsonl. Failures leave the file unchanged (#373).
  • --sharing / --no-sharing on opentide setup and opentide setup ci. The generated job is opentide share push --changed, after generate, on a push to the default branch. Deploy does not wait for it (#375).

Changed

  • Regenerated GitHub workflows compare github.ref to 'refs/heads/<branch>'.
  • share preview does not require the API key. push and retract still do.

Verify

python -c "import opentide; print(opentide.__version__)"
opentide share --help

Expect 0.7.0.

Links

Assets 2
Loading