release: sync SDK + MCP to omnigraph-server v0.8.1

[aaltshuler]

Scripted sync to the v0.8.1 engine tag, following #13's pattern:

• omnigraph.serverVersion → 0.8.1; sync-spec fetched the tag's openapi.json (check-drift clean).
• The wire surface is unchanged — the spec delta is exactly the info.version line, so generate produced no type changes (only version.gen.ts).
• Package versions → 0.8.1 (check-versions green); the MCP health test's pinned sdkServerVersion updated.
• Full build + tests green (SDK 86 passed, MCP 14 passed).

Engine v0.8.1 highlights relevant to SDK users: filtered nearest()/bm25() now applies filters before the search (result sets change — previously missing rows appear), undirected traversal $a <edge> $b in .gq, enum widening in schema migration. All are query/engine-level — no SDK API changes.

Greptile Summary

This PR is a scripted version bump from 0.8.0 to 0.8.1 across the SDK and MCP packages, syncing to the omnigraph-server v0.8.1 engine tag. The OpenAPI spec delta is limited to info.version, so no type generation occurred and no wire-surface changes were introduced.

• Six files updated: root package.json (serverVersion), both package.json manifests, spec/openapi.json, packages/sdk/src/version.gen.ts, and the MCP health test's sdkServerVersion assertion.
• packages/mcp/src/version.gen.ts was not regenerated: the gen-version script updates both the SDK and MCP version files together, but only the SDK file appears in the diff — MCP_PACKAGE_VERSION still reads \"0.8.0\", so the MCP server will advertise the wrong version in the MCP initialize handshake.
• The test asserting the MCP server's initialize version (line 94) was also left at '0.8.0', keeping it consistent with the stale generated file but masking the discrepancy from CI.

Confidence Score: 3/5

The MCP server will ship advertising version 0.8.0 to clients even though the package declares 0.8.1, because the auto-generated version constant was not regenerated.

The packages/mcp/src/version.gen.ts file was not regenerated — it remains at MCP_PACKAGE_VERSION = "0.8.0" while everything else moved to 0.8.1. The MCP server embeds this constant directly in the MCP protocol handshake, so every client that connects will receive the wrong version. The test at line 94 was left unchanged, meaning this discrepancy passes CI silently.

packages/mcp/src/version.gen.ts needs to be regenerated via pnpm gen-version, and the test assertion in packages/mcp/test/server.test.ts line 94 needs to be updated to '0.8.1'.

Important Files Changed

Filename	Overview
packages/mcp/src/version.gen.ts	Auto-generated file not regenerated — still exports MCP_PACKAGE_VERSION = "0.8.0" while the package was bumped to 0.8.1, causing the MCP server to advertise the wrong version to clients
packages/mcp/test/server.test.ts	sdkServerVersion assertion correctly updated to 0.8.1; the server initialize version assertion at line 94 was not updated and will diverge once version.gen.ts is regenerated
packages/sdk/src/version.gen.ts	Correctly regenerated — SERVER_VERSION updated from 0.8.0 to 0.8.1
spec/openapi.json	Only info.version changed (0.8.0 to 0.8.1); no wire-surface changes, consistent with the PR description
package.json	Root omnigraph.serverVersion bumped to 0.8.1 — source of truth for check-versions and gen-version scripts
packages/sdk/package.json	SDK package version bumped to 0.8.1, consistent with root serverVersion
packages/mcp/package.json	MCP package version bumped to 0.8.1 — but the corresponding version.gen.ts was not regenerated

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["root package.json
omnigraph.serverVersion = 0.8.1"] --> B["scripts/gen-version.ts"]
    C["packages/mcp/package.json
version = 0.8.1"] --> B
    B --> D["packages/sdk/src/version.gen.ts
SERVER_VERSION = 0.8.1 (updated)"]
    B --> E["packages/mcp/src/version.gen.ts
MCP_PACKAGE_VERSION = 0.8.0 (NOT regenerated)"]
    D --> F["SDK reports correct version"]
    E --> G["McpServer init handshake
reports 0.8.0 instead of 0.8.1"]
    E --> H["Test line 94 still asserts 0.8.0
masks the stale value"]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["root package.json
omnigraph.serverVersion = 0.8.1"] --> B["scripts/gen-version.ts"]
    C["packages/mcp/package.json
version = 0.8.1"] --> B
    B --> D["packages/sdk/src/version.gen.ts
SERVER_VERSION = 0.8.1 (updated)"]
    B --> E["packages/mcp/src/version.gen.ts
MCP_PACKAGE_VERSION = 0.8.0 (NOT regenerated)"]
    D --> F["SDK reports correct version"]
    E --> G["McpServer init handshake
reports 0.8.0 instead of 0.8.1"]
    E --> H["Test line 94 still asserts 0.8.0
masks the stale value"]

Loading

Comments Outside Diff (1)

1. packages/mcp/test/server.test.ts, line 94 (link)

   MCP server version assertion not updated to match new package version

   The test checks the version reported by the MCP server in the initialize handshake, which is sourced from MCP_PACKAGE_VERSION in packages/mcp/src/version.gen.ts. Once version.gen.ts is regenerated to 0.8.1, this assertion will fail. Update it now so it stays consistent with the package bump.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

   

_{Reviews (1): Last reviewed commit: "release: sync SDK + MCP to omnigraph-ser..." | Re-trigger Greptile}