release: SDK 0.6.1 — sync to engine v0.6.1 (stored-queries support)#11
Merged
Conversation
Aligns the TypeScript SDK with omnigraph-server v0.6.1 (was 0.6.0), which
adds the stored-queries API. Closes the version-lag half of
iss-dx-ts-no-releases.
- Bump root omnigraph.serverVersion + both packages to 0.6.1; regenerate
version.gen.ts (check-versions passes).
- sync-spec: vendor the engine's v0.6.1 openapi.json and regenerate the
typed client (check-drift passes).
- New surface for the two added operations (coverage now 19/19):
- `og.queries.list()` → GET /queries (typed stored-query catalog).
- `og.queries.invoke(name, input?)` → POST /queries/{name} (runs a
server-side stored query; returns Read | Change). params/rows kept
opaque across the camel<->snake boundary, mirroring og.query().
- Export Queries / QueryCatalogEntry / ParamDescriptor / InvokeQuery /
InvokeQueryInput types and the ParamKind enum.
- Add queries.test.ts; bump the two version-coupled MCP test assertions.
MCP tool surface is intentionally unchanged — exposing stored queries as
MCP tools is a separate follow-up. Publishing is gated on a maintainer
pushing the v0.6.1 tag and approving the `release` environment.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Bumping the pinned server to 0.6.1 makes the e2e job install a server that enforces the config-coherence check: a named graph plus a top-level `policy.file` is rejected (the top-level block would be silently ignored). The single-graph fixture hit exactly that and the server refused to start. Move `policy.file` into `graphs.e2e.policy.file` (the multi-graph fixture already uses the per-graph shape). Unblocks the e2e job at server 0.6.1. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The TS SDK was pinned to omnigraph-server 0.6.0 while the engine shipped 0.6.1 — the version-lag half of iss-dx-ts-no-releases (P3). v0.6.1 isn't a no-op bump: it adds the stored-queries API (
GET /queries,POST /queries/{name}), so the SDK must vendor the new spec and expose the surface.What
omnigraph.serverVersion+@modernrelay/omnigraph+@modernrelay/omnigraph-mcp→0.6.1; regeneratedversion.gen.ts. (check-versions✅)sync-specvendored the engine's v0.6.1openapi.json; regenerated the typed client. (check-drift✅)og.queries.list()→GET /queries— the typed stored-query catalog (themcp.exposesubset).og.queries.invoke(name, input?)→POST /queries/{name}— runs a server-side stored query by name; returnsRead | Change.params(body) androws/columns(read response) stay opaque across the camel↔snake boundary, exactly likeog.query(). Distinct fromog.query(), which runs ad-hoc GQ source.Queries,QueryCatalogEntry,ParamDescriptor,InvokeQuery,InvokeQueryInputtypes + theParamKindruntime enum.queries.test.ts(list + invoke, incl. path escaping and opaque-key round-trip); bumped two version-coupled MCP assertions.Gates run locally:
check-versions,check-drift,check-coverage,build,typecheck,test(SDK 85 passed, MCP 16 passed) — all green. Lockfile unchanged.Scope notes
v0.6.1tag and approves thereleaseenvironment; the workflow then publishes npm and (via the just-merged ci(release): create a GitHub Release on each published tag #10) creates the GitHub Release.🤖 Generated with Claude Code