Verified 2026-08-01

Release status

opentine v0.5.0 is the current public release on GitHub and PyPI. v0.6.0 is in development, not a published package or a second set of production guarantees.

Use v0.5.0 for published behavior

python -m pip install --upgrade "opentine==0.5.0"
python -c "import opentine; print(opentine.__version__)"

• The tagged release is v0.5.0, and the exact wheel and source distribution are on PyPI.
• Supported Python remains Python 3.11–3.14; portable artifacts remain.tine v2, and repository objects remainv3.
• The tagged changelog is the source of truth for shipped commands, integrations, and compatibility claims.

What v0.6.0 in development means

The Surface Release is being developed in public: repository engines are moving into operator and CI-friendly CLI verbs alongside replay verification, scriptable diff, and cross-run statistics. It is not tagged or published to PyPI, and it does not change the storage formats.

Everything in this section is verified on the public development branch, but it is unreleased. Do not use these commands as v0.5.0 instructions or expect a v0.6.0 wheel from PyPI yet.

Implemented on the development branch

• Repository operations become direct CLI verbs: repo-show,context, repo-diff, repo-search,attest, evaluate, promote,repo-fork, and repo-resume, plus JSON output forrepo-log.
• tine replay --verify turns deterministic cached replay into a CI verdict; harness mode can execute twice to detect external-agent drift.
• tine diff --json --exit-code exposes scriptable drift, whiletine stats aggregates indexed runs with the same filters astine ls.
• Import and tag gain JSON surfaces, and public diff, query, and signing APIs gain top-level re-exports.

Compatibility work continues

The branch adds artifacts and a repository generated by the published v0.5.0wheel to the golden compatibility suite. Future builds must load and verify data from v0.3.0, v0.4.0, and v0.5.0. No portable-artifact or repository-format bump is proposed.

• Follow the draft Surface Release pull request.
• Read the development changelog and inspect the exact compatibility-gate commit.
• Review the live v0.5.0-to-branch comparisonor browse the development branch directly.

Not part of the v0.6.0 preview

Managed-cloud Bedrock, Vertex AI, and Azure work was explicitly deferred because it could not be validated against live endpoints. The website does not present it as a current or upcoming capability.

Product versions are not format versions

“v0.6.0” names the next opentine product line. It does not mean.tine format v0.6.0 or repository format v0.6.0. Until an official release explicitly changes them, the documented storage contracts remain portable v2 and repositoryv3. Development metadata and APIs can still change before release.