FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

chore(deps): Update graphrag-sdk requirement from <0.9.0,>=0.8.1 to >=0.8.1,<1.2.0 by dependabot[bot] · Pull Request #673 · FalkorDB/code-graph · GitHub

/ code-graph Public

chore(deps): Update graphrag-sdk requirement from <0.9.0,>=0.8.1 to >=0.8.1,<1.2.0 - #673

Merged
gkorland merged 1 commit into
stagingfrom
dependabot/pip/staging/graphrag-sdk-gte-0.8.1-and-lt-1.2.0
Aug 23, 2026
ConversationCommits (1)ChecksFiles changed
Merged

chore(deps): Update graphrag-sdk requirement from <0.9.0,>=0.8.1 to >=0.8.1,<1.2.0#673
gkorland merged 1 commit into
stagingfrom
dependabot/pip/staging/graphrag-sdk-gte-0.8.1-and-lt-1.2.0

Conversation

dependabot Bot commented on behalf of github May 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Updates the requirements on graphrag-sdk to permit the latest version.

Release notes

Sourced from graphrag-sdk's releases.

v1.1.0

What's Changed

New Contributors

Full Changelog: FalkorDB/GraphRAG-SDK@v1.0.2...v1.1.0

Changelog

Sourced from graphrag-sdk's changelog.

[1.1.0] - 2026-05-05

Adds incremental ingestion primitives and a CI-friendly batch wrapper. Built around a crash-safe state-machine cutover (idempotent rollforward keyed off a ready_to_commit marker on the pending Document node) so mid-flight failures recover correctly on retry. Documents the cost model so consumers can pick a sensible finalize() cadence. Closes a pre-existing silent-correctness bug in fuzzy resolvers (MENTIONED_IN edges were dropped for any merged entity). No breaking changes; one previously-rejected argument shape (document_id in file mode) is now accepted.

Added

  • GraphRAG.update(source=..., text=..., document_id=..., if_missing=...) and update_sync() — re-sync a previously-ingested document without rebuilding the rest of the graph. SHA-256 content-hash short-circuits no-op updates: a touch-only PR (CRLF, formatter-only changes) costs roughly one Cypher lookup.

    Cutover is a documented state machine (EMPTY → WRITING → WRITTEN → COMMITTED → FINAL) with a single load-bearing transition: setting ready_to_commit = true on the pending Document node. That is the commit point — it is one Cypher statement (atomic at the per-statement level FalkorDB does guarantee), and it must complete before any destructive op touches the live document. Once committed, recovery on crash is rollforward (each post-commit op is idempotent) rather than rollback. The practical effect: an update() interrupted by a transient failure retries cleanly instead of raising DocumentNotFoundError against a half-deleted document.

    Cleans up entities orphaned by the change (zero remaining MENTIONED_IN, scoped to entities the prior version of the document referenced) along with their incident RELATES edges; entities still referenced by other documents are preserved.

  • GraphRAG.delete_document(document_id) and delete_document_sync() — remove one document's chunks and the Document node, plus orphaned entities scoped to that document. Other documents' data is untouched.

  • GraphRAG.apply_changes(added=..., modified=..., deleted=..., max_concurrency=3, update_concurrency=1) and apply_changes_sync() — convenience batch dispatcher for CI-driven incremental ingestion. Routes each list to the right primitive (ingest for added, update(if_missing="ingest") for modified, delete_document for deleted). Per-file failures are collected, not raised — matching ingest()'s batch contract. Does not call finalize(); that stays the caller's responsibility so a

... (truncated)

Commits
  • bfa6271 Merge pull request #247 from FalkorDB/feat/incremental-updates-v1.1.0
  • 518c7cc fix(v1.1.0): RELATES source_chunk_ids unioned on upsert, not overwritten
  • 47bc116 fix(v1.1.0): Phase 0 rollforward also raises on missing content_hash
  • fd2c1f9 style: ruff format -- api/main.py + storage/graph_store.py
  • 9b51015 fix(ci): integration suite green -- LLM script, recovery snapshot
  • 205dec7 fix(ci): lint + my new tests (graph_name, MockLLM import)
  • 569d886 fix(v1.1.0): bot-review followups -- update/ingest path, CI, docs
  • f844912 fix(v1.1.0): crash-safe orphan + stale-RELATES cleanup (PR #247 review)
  • ec3e31d Merge main into feat/incremental-updates-v1.1.0
  • 9c2be5c docs(v1.1.0): README + CHANGELOG + example review fixes
  • Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels May 12, 2026
dependabot Bot mentioned this pull request May 12, 2026
Closed

gkorland commented May 12, 2026

Copy link
Copy Markdown
Contributor

@copilot should the uv.lock updated too?

Copilot AI commented May 12, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

@copilot should the uv.lock updated too?

Yes — I updated uv.lock as well and regenerated it with graphrag-sdk resolved to 1.1.0 in commit f3467c8.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • 0.0.0.0.in-addr.arpa
    • Triggering command: /usr/local/bin/node node server.js (dns block)
  • roslynomnisharp.blob.core.windows.net
    • Triggering command: /home/REDACTED/work/code-graph/code-graph/.venv/bin/python3 /home/REDACTED/work/code-graph/code-graph/.venv/bin/python3 -m pytest tests/ --verbose (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Copilot AI requested a review from gkorland May 12, 2026 17:38

dependabot Bot commented on behalf of github Jun 3, 2026

Copy link
Copy Markdown
Contributor Author

A newer version of graphrag-sdk exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

gkorland previously approved these changes Jun 7, 2026
View reviewed changes
gkorland mentioned this pull request Aug 23, 2026
Merged
chore(deps): Update graphrag-sdk requirement
a75e736 
Updates the requirements on [graphrag-sdk](https://github.com/FalkorDB/GraphRAG-SDK) to permit the latest version.
- [Release notes](https://github.com/FalkorDB/GraphRAG-SDK/releases)
- [Changelog](https://github.com/FalkorDB/GraphRAG-SDK/blob/main/CHANGELOG.md)
- [Commits](FalkorDB/GraphRAG-SDK@v0.8.1...v1.1.0)

---
updated-dependencies:
- dependency-name: graphrag-sdk
  dependency-version: 1.1.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
gkorland force-pushed the dependabot/pip/staging/graphrag-sdk-gte-0.8.1-and-lt-1.2.0 branch from f3467c8 to a75e736 Compare August 23, 2026 21:04
gkorland merged commit 655d0b8 into staging Aug 23, 2026
12 checks passed
gkorland deleted the dependabot/pip/staging/graphrag-sdk-gte-0.8.1-and-lt-1.2.0 branch August 23, 2026 21:14
gkorland mentioned this pull request Aug 24, 2026
Merged
YogeLiu pushed a commit to YogeLiu/code-graph that referenced this pull request Aug 26, 2026
fix(deps): pin graphrag-sdk to <0.9.0 and build image from uv.lock
cc7ee4e 
graphrag-sdk 1.x is a full rewrite that removed `graphrag_sdk.models`
and the `Ontology`/`KnowledgeGraph`/`KnowledgeGraphModelConfig` public
API that `api/llm.py` depends on. FalkorDB#673 widened the constraint to
`<1.2.0`, so a fresh resolve picks 1.1.1 and the app crashes on import:

    File "/app/api/llm.py", line 7, in <module>
      from graphrag_sdk.models.litellm import LiteModel
    ModuleNotFoundError: No module named 'graphrag_sdk.models'

CI stayed green because `uv sync` honours uv.lock (still 0.8.2), while
the Docker image ran `pip install .` straight from pyproject.toml and
resolved the newest allowed version. Restore the `<0.9.0` upper bound
and install the image's dependencies under constraints exported from
uv.lock so the container can no longer drift from the lockfile.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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
Show hidden characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

gkorland gkorland left review comments

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

Back | FazBrowse Home | New Git URL