Skip to content

Versions and channels

How to pick the right OntoCode / OntoCore build. Pin production and CI to a tagged release; do not follow main docs alone.

Source of truth

Source What it means
docs/TAGGED_RELEASE Canonical public install version (today: 0.26.2)
GitHub Releases VSIX, Linux CLI tarball, multi-platform LSP, tutorial zip, checksums
crates.io Published Rust crates and cargo install ontocore-cli
VS Code Marketplace Extension for VS Code (manual publish; usually matches the tag within hours)
Open VSX Extension for Cursor / Open VSX clients
Read the Docs latest Built from the default branch (main) — may describe work after the last tag

How to check which version you have

Surface How
VS Code / Cursor extension Extensions view → OntoCode → version under the title (or ontocode.ontocode in the extension details)
CLI ontocore --version (or ontocore -V)
Language server Output → OntoCore Language Server often logs the binary path; or run the bundled ontocore-lsp with --version if you know its path

If Marketplace / Open VSX is behind GitHub, install the release VSIX for the tag you need — see below.

Goal Command / link
VS Code Marketplace or download ontocode-v0.26.2.vsix from GitHub Releases
Cursor Open VSX or the same VSIX
CLI (pinned) cargo install ontocore-cli --locked --version 0.26.2
CLI (Linux, no compile) ontocore-v0.26.2-x86_64-unknown-linux-gnu.tar.gz from GitHub Releases
Tutorial files (offline) ontocode-tutorial.zip on the same GitHub Release (or curl samples in First success)

Always pin: bare cargo install ontocore-cli resolves to the latest crates.io version and can jump without your review.

When Marketplace lags GitHub

Marketplace publish is always manual after the release workflow finishes. Open VSX publishes automatically when OVSX_PAT is set (see Marketplace publish). Either store can lag the GitHub tag by hours or longer.

Playbook: store version ≠ latest tag

  1. Check the latest GitHub Release tag (example: v0.26.2).
  2. In VS Code / Cursor: Extensions → OntoCode — note the installed version.
  3. If the store is older than the tag you need:
  4. Download ontocode-v<version>.vsix from that Release.
  5. Extensions → … → Install from VSIX…
  6. Reload the window.
  7. Confirm the extension version matches the tag under the Extension details.
  8. Keep CI pinned with cargo install ontocore-cli --locked --version <tag> (or the Linux tarball) — do not wait for Marketplace for automation.

Re-check Marketplace / Open VSX before an org-wide rollout. Capability truth by version: What ships today. Upgrades: Migration guides.

Maintainer notes: Marketplace publish.