Upgrade @modernrelay/omnigraph to ^0.8.0#18
Merged
Merged
Conversation
Prod (graph.modernrelay.ai) already serves 0.8.0. The SDK surface is nearly identical (health gains internal_schema_version); none of the facade's call paths changed shape. Note: the SDK still reads camelCase `mergeConflicts` from an error body the server sends as snake_case `merge_conflicts`, so ConflictError's structured conflicts remain always-undefined in 0.8.0 — the raw-body fallback in our Client facade stays load-bearing. Verified live against prod 0.8.0 (dev-graph notebook, reads) and a 0.7.1 local demo (cross-line read+write round-trip). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011TrhtF1SiJghJASMWECzBh
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
Greptile: @modernrelay/omnigraph@0.8.0 declares engines.node >=22 while the workspace and published CLI still advertised >=20 — a Node 20 install could fail strict engine checks or hit 22-only runtime APIs. The workspace root, the published CLI, and CLAUDE.md now all say >=22. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011TrhtF1SiJghJASMWECzBh
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.
Prod (
graph.modernrelay.ai) already serves 0.8.0; this brings the SDK to the matching line. The 0.8 type surface is nearly identical (health output gainsinternal_schema_version) and none of the facade's call paths changed shape — the diff is the two dependency declarations + lockfile.Upstream bug still present in 0.8.0 (worth reporting): the SDK constructs
ConflictError.mergeConflictsfrombody?.mergeConflicts, but the server sends snake_casemerge_conflictsand error bodies are never camelized — so the field is alwaysundefined. Our Client facade's raw-body fallback (from the branch-staging work) remains load-bearing.Verified live: prod 0.8.0 (dev-graph notebook — all cells,
✓ valid notebook) and cross-line against a 0.7.1 local demo (read + write round-trip). Full suite green.🤖 Generated with Claude Code
https://claude.ai/code/session_011TrhtF1SiJghJASMWECzBh
Greptile Summary
This PR upgrades the notebook packages to the OmniGraph 0.8 SDK line.
@modernrelay/omnigraphto^0.8.0in the CLI and client packages.0.8.0.>=22.Confidence Score: 5/5
This looks safe to merge.
Important Files Changed
>=22.0.8.0with its recorded Node engine requirement.>=22.Reviews (2): Last reviewed commit: "Align the Node engine contract with the ..." | Re-trigger Greptile
Context used: