Repository navigation
release: sync SDK + MCP to omnigraph-server v0.11.0 - #20
Merged
Merged
Conversation
- serverVersion 0.11.0; spec/openapi.json synced from the v0.11.0 tag; generated types and SERVER_VERSION regenerated; both packages at 0.11.0 - og.readiness(): GET /readyz (new in v0.11), a flat unauthenticated path; a draining server's 503 is returned as data, not thrown - exported Readiness, BranchOutcome (Change.outcome, from branch statements on POST /mutate) and SystemColumns (Schema.systemColumns) - MCP cookbook: expose upstream changes.md (commits, change feeds, v0.11 branch statements); skip blobs.md (blob cells are read through /blob, which the MCP does not wrap)
… identity, receipt semantics, docs
…tection uses the engine's whitespace
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.
Syncs
@modernrelay/omnigraphand@modernrelay/omnigraph-mcptoomnigraph-serverv0.11.0 (released 2026-09-13), following the README's release workflow.What changed
package.json#omnigraph.serverVersion→0.11.0;spec/openapi.jsonsynced from thev0.11.0tag;packages/sdk/src/generated/and bothversion.gen.tsregenerated; both packages at0.11.0.og.readiness()— binds the one new operation,GET /readyz(readiness). It is a flat, unauthenticated path like/healthz(added toFLAT_PATHS), and a draining server answers 503 with the same body, soreadiness()returns it (acceptedStatuses: [503]) instead of throwing. Other failures still throw.Readiness,BranchOutcome(Change.outcome, set whenPOST /mutateruns a branch statement — RFC 0055) andSystemColumns(Schema.systemColumns).changes.mdandblobs.md.changesis exposed (the MCP hascommits_changes,changes_polland conditionalmutate);blobsis skipped (blob cells are read through/blob, which the MCP does not wrap).Checks (local, Node 24)
check-release,check-coverage(26 of 29 operations bound, 3 intentionally unbound),build,typecheck,test— SDK 131 passed / 24 skipped (e2e, needs a server), MCP 22 passed. The e2e workflow on this PR runs the suite against the v0.11.0 release binary.Why now
Tower (ModernRelay/tower) pins this SDK as the newest engine it supports; both production clusters already run 0.11.0, and Tower's move to 0.11 is blocked on this release (Tower specs/079). Nothing is tagged or published by this PR — cut
v0.11.0after review as usual.