Release notes from neotoma
Articles sur Release notes from neotoma
Release v0.25.0 · markmhendrickson/neotoma
Install npm https://www.npmjs.com/package/neotoma/v/0.25.0 Compare v0.24.0 → v0.25.0 — view diff This minor release makes update_schema_incremental write to the schema scope it actually read, so incremental schema updates stop losing fields. It adds a repo argument, an allowlist and a dry run to issue sync, and it retires the query-memory and store-data wrapper skills. It also fixes the capability manifest so upgrade checks from v0.24.0 report the two new relationship-type tools.
Release v0.24.0 · markmhendrickson/neotoma
Install npm https://www.npmjs.com/package/neotoma/v/0.24.0 Compare v0.23.1 → v0.24.0 — view diff This release tightens tenant isolation and agent identity across schema resolution, provenance reads, entity writes, AAuth grants and shared-graph sign-in, binds the server to loopback by default, adds a runtime relationship-type registry so the edge vocabulary is no longer a fixed enum, ships a new MCP 2026-07-28 stateless transport alongside the existing session-based one,
Release v0.23.1 · markmhendrickson/neotoma
Install npm https://www.npmjs.com/package/neotoma/v/0.23.1 Compare v0.23.0 → v0.23.1 — view diff Two fixes: MCP sessions whose identity is not yet resolved at initialize are no longer told an instance has no skills and no standing rules, and a schema-declared store_warnings rule can no longer block a write.
Release v0.23.0 · markmhendrickson/neotoma
Install npm https://www.npmjs.com/package/neotoma/v/0.23.0 Compare v0.22.2 → v0.23.0 — view diff This release ships one feature and three fixes: hosted-instance skills are now visible to MCP-only agents at session start, a stale MCP session id no longer breaks the whole client instead of just that one session, scalar correction tie-breaks now pick the newer write instead of an arbitrary one, and a CLI test process can no longer silently read and write a real operator's data directory.