Skip to content

v2.13.0

Choose a tag to compare

@github-actions github-actions released this 21 Oct 06:09
41a9022

Added

  • gno convert <file> prints the Markdown GNO would index for one file, without config or an index, and the SDK exposes the same as convertFile(path). The output, and its mirrorHash with --json, equal what gno update stores for the same file. Mail archives, calendars and other multi-record formats are refused with MULTI_DOCUMENT. Thanks to @ArnauvGilotra for the idea and the original pull request (#314).
  • gno search, gno vsearch and gno query can search several collections at once: repeat -c (-c work -c notes), or pass collections to the MCP tools, POST /api/search and POST /api/query, and the SDK. The filter applies before the result limit, so other collections never take result slots, and responses list the collections in meta.collections. Up to 256 names per request; collection and collections cannot be combined. Over the resident HTTP MCP endpoint, the egress check covers just the listed collections. Thanks to @ArnauvGilotra for the idea and the original pull request (#313).
  • Reindex only some files: paths on MCP gno_sync / gno_index and REST POST /api/sync, and gno index <collection> --path <file...>. A listed file that no longer exists is removed from the index. Up to 256 files per request (directories are rejected); waiting path requests that add up to more become one whole-collection pass.
  • Reindex requests that arrive while another job runs are queued instead of refused. Requests for the same collection that arrive while one waits join it and share its job id, so many requests cause at most one more pass. Job status reports queued and the merged scope; too many waiting requests return QUEUE_FULL. The Web UI shows a queued reindex and keeps following it. Thanks to @DanielKillenberger for the queue and path-level reindexing (#336).

Fixed

  • Over the resident HTTP MCP endpoint (gno serve, gno daemon), a tool call naming a collection that is not configured (for example gno_search with collection: "typo") returns the tool's Collection not found error instead of 500 Internal MCP transport error. The egress check ignores unknown names and, when none of the named collections exist, checks every configured collection.
  • MCP retrieval tools read only committed index data while a sync is writing, instead of possibly seeing a batch that is later rolled back. Thanks to @DanielKillenberger for the fix (#333).