Skip to content

Migration guide — v0.15.0

Summary

v0.15 expands the v0.14 plugin host MVP into a versioned plugin API with explicit permissions, richer UI contributions (views, preference pages, context actions), and improved explanation workflows (multiple alternatives + staleness metadata).

New capabilities

Feature How to use
Plugin permissions Add permissions = ["workspace.read", ...] to your plugin manifest
Plugin UI views Add ui.views contributions; open via OntoCode Plugins: Open View…
Run view action LSP ontocore/runPlugin with action: "ui_view" and view_id
Explanation alternatives OntoCode explanation panel shows multiple justifications (when available)
Explanation caching + staleness Explanation payloads include indexed_at and content_hash to detect stale results

Breaking changes

None expected for typical v0.14 users.

Plugin manifests without permissions

v0.15 introduces permission enforcement for plugins. Manifests should now declare permissions.

To avoid breaking older manifests, the host provides a backward-compatible default for manifests that omit permissions (intended only as a transition path). New plugins should always declare permissions explicitly.

Upgrade steps

  1. Update ontocore CLI: cargo install ontocore-cli --locked
  2. Update OntoCode extension to 0.15.0
  3. If you use plugins:
  4. Add permissions = [...] to each manifest under .ontocore/plugins/*.toml
  5. Optionally add UI contributions under [ui] (views, commands, etc.)

See: