Repository navigation
chore: rename project to graph-kit (@graph-kit/*) - #75
Merged
Merged
Conversation
Rename the monorepo from graph-om to graph-kit and republish scope as @graph-kit. - Root package: graph-om -> graph-kit (private), bin graph-kit - Packages: @graph-om/* -> @graph-kit/* (cli, sdk, zod, mcp, migrate, testing) - All imports, docs, tests, changeset linked set, turbo env vars, vitest aliases, docker names, and graph-kit.config.ts files updated - pnpm-lock.yaml regenerated (workspace links updated) Not yet published to npm (requires npm auth).
|
Important Review skippedToo many files! This PR contains 304 files, which is 204 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. Usage-priced reviews support at most 300 files.
|
| await runNeo4j(); | ||
|
|
||
| console.log('\n--- Multi-driver: Memgraph (config only) ---'); | ||
| console.log('config:', JSON.stringify(memgraphConfig())); |
| ); | ||
|
|
||
| console.log('\n--- Multi-driver: FalkorDB (config only) ---'); | ||
| console.log('config:', JSON.stringify(falkordbConfig())); |
size-limit report 📦
|
The rename from @graph-om to @graph-kit adds one character per @graph-kit occurrence, pushing @graph-kit/mcp (require) 23 B over its 1700 B limit. Increase limit to 1800 B with buffer.
The CLI init command was scaffolding graph.config.ts but the test expects graph-kit.config.ts. Also fix generate.ts to prefer graph-kit.config.ts as config candidate, fix error message reference, and replace legacy metal.config.ts watch target.
Add explicit CodeQL analysis workflow so code scanning works correctly after the repository rename from graph-om to graph-kit. The previous repo-level default setup was tied to the old repo name and failed immediately on the renamed repo.
Remove advanced CodeQL workflow files. CodeQL is configured at the GitHub repo level via default setup, which needs to be re-enabled in Settings > Security > Code scanning for the renamed graph-kit repo. An advanced-setup workflow conflicts with the enabled default setup.
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
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.
Rename the monorepo from graph-om to graph-kit and republish the scope as @graph-kit.
Changes
graph-om->graph-kit(private), bingraph-kit@graph-om/*->@graph-kit/*(cli, sdk, zod, mcp, migrate, testing)graph-kit.config.tsfiles updatedpnpm-lock.yamlregenerated (workspace links updated)Verification
@graph-kit/sdkbuild: success; tests 223 passed@graph-kit/clibuild: successUsage: graph-kitbin test)pnpm lint: 0 errors@graph-om/graph-omreferences remain in sourcePublishing
Not yet published to npm — requires
npm login(current token is 401). Runpnpm release(turbo build + changeset publish) after authenticating.Note
GitHub repo URL still points to
frontal-labs/graph-om.git; the repo itself would need to be renamed tograph-kiton GitHub separately.