Skip to content

Releases

v0.3.0

v0.3.0 Latest
Latest

Choose a tag to compare

View all tags
@ofonseca-pyming ofonseca-pyming released this 04 Nov 20:28
v0.3.0
9143ddf

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.

Assets 4
Loading

odools-mcp 0.2.0

odools-mcp 0.2.0

Choose a tag to compare

View all tags
@ofonseca-pyming ofonseca-pyming released this 03 Nov 20:54
v0.2.0
284f813

odools-mcp 0.2.0

MCP adapter (for OpenCode, Claude Code and Codex) over the official, unmodified OdooLS 1.6.1 stable: status, definition, declaration, references, hover and file_diagnostics for Odoo workspaces.

Install

Self-contained Linux x64 bundle with precompiled adapter files and exact-lock production dependencies. It needs Node.js >= 20 (tested only on Node 26.9.0) and no checkout, npm ci, build or network for the adapter itself. It does not include Node or the OdooLS/TypeScript runtime; install and verify that separately.

sha256sum -c pyming-odools-mcp-0.2.0-linux-x64-bundle.tar.gz.sha256
mkdir odools-mcp-0.2.0
tar -xzf pyming-odools-mcp-0.2.0-linux-x64-bundle.tar.gz -C odools-mcp-0.2.0
CLI=./odools-mcp-0.2.0/node_modules/@pyming/odools-mcp/dist/cli.js
node "$CLI" --version --json
node "$CLI" install-runtime --version 1.6.1 --runtime-dir "$HOME/.local/share/odools-mcp/runtime-1.6.1"
node "$CLI" verify-runtime --runtime-dir "$HOME/.local/share/odools-mcp/runtime-1.6.1"

A runtime already installed by 0.1.0 for the exact pinned 1.6.1 / TypeScript 6.0.2 assets is accepted read-only after full verification; it is not reinstalled. See the README for MCP client configuration (use node plus the absolute CLI path).

SHA-256

e53559533641996ed0e53b64ec8664bd15abbd6fafa41109eff0d1c26337c302 pyming-odools-mcp-0.2.0-linux-x64-bundle.tar.gz

Changes

  • Managed runtime pin moves from OdooLS 1.5.2 Beta to 1.6.1 stable.
  • Adapter identity (version, build provenance, runtime pins) is exposed in the CLI, MCP initialization and status.
  • Reproducible candidate packaging, a native release gate and a fix for the JavaScript availability diagnostic.
  • Local pre-commit source gate.

Provenance

Built from commit 284f813d5a74184ca97dfaeece9bf41bbc8882f5 in formal mode on a clean tree. Two isolated builds produced byte-identical bundles; that claim covers those two builds only. The native release gate passed 27/27 against the extracted bundle with the default managed 1.6.1 runtime. PROVENANCE.json contains published: false; this records build-time state and is not a statement about this release.

The package remains private: true (no npm publication).

Loading