Skip to content

v0.3.0

Latest

Choose a tag to compare

@ofonseca-pyming ofonseca-pyming released this 04 Nov 20:28

Odoo-aware navigation and source discovery

This release expands the read-only MCP catalog from six to eight tools:

  • workspace_symbols: bounded known-name lookup over OdooLS's loaded analysis state, including model aliases, local XML IDs and OWL template names.
  • document_symbols: bounded file outlines for Python/PYI, XML, JavaScript and TypeScript.

It also adds:

  • Static backend-capability observation and safer protocol handling, including UTF-16 negotiation and explicit refusal of reverse edit requests.
  • JavaScript hover with bounded documentation and snapshot/generation safety. TypeScript hover is explicitly unsupported; TypeScript outlines are supported.
  • Exact optional diagnostic codes and sources, without changing publication freshness semantics or clean: null.
  • Official, unmodified OdooLS 1.6.2, including the disconnect/orphan-process and @api.returns fixes. Managed TypeScript/tsserver remains exactly 6.0.2.
  • First-time Odoo developer onboarding with explicit executable paths, compatible runtime/configuration recipes and clearer troubleshooting.

Installation and compatibility

Managed runtime platform: Linux x64, with Node.js 20 or newer. Runtime installation is separate; the bundle contains the adapter and exact-lock production dependencies, not Node or OdooLS. No npm registry publication is provided.

Use the pyming-odools-mcp-0.3.0-linux-x64-bundle.tar.gz asset and its matching SHA-256 file. Follow the version-matched README shipped with the release. Adapter 0.3.0 requires OdooLS 1.6.2; it must not be pointed at a retained 1.6.1 runtime as if compatible. Keep adapter 0.2.0 + OdooLS 1.6.1 together for rollback.

The catalog is status, definition, declaration, references, hover, file_diagnostics, workspace_symbols, and document_symbols. There are no completion, command-execution, edit or generic LSP tools. Symbol results are not conceptual search, exhaustive discovery, or live Odoo registry/database evidence.

Verification

The formal release bundle is built twice from its clean, identified source revision and must be byte-identical. Publication is gated on extracted-package native acceptance on Node 26.9.0 and Node 20.20.2, covering 38 mandatory outcomes per route, including genuine Odoo 18 @api.returns semantics, abrupt adapter death/backend-tree exit, diagnostics issue/restoration and cleanup.

Bundle PROVENANCE.json records build-time published: false; this is not a statement about GitHub release visibility. Do not edit or repack the authenticated archive to change that field.

After changing the installed adapter command, reconnect the MCP or use OpenCode /reload. Running processes retain loaded code. PYMING harness rollout is a separate authenticated manifest update; publication alone does not activate installations.