chore(release): prepare v1.4.0 - #293
Merged
Merged
Conversation
Bump version to 1.4.0 and cut the [Unreleased] section into [1.4.0]: the chunk-level extraction cache for update() (#288) and the DatabaseError / DatabaseUnavailableError contract that backs it. Also bump graphrag_sdk.__version__, which was left at 1.2.0 when 1.3.0 was cut — it is what the API's /version endpoint reports. Minor bump — the cache is opt-in (cache_unchanged_chunks=False by default) and existing ingest paths are unaffected. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe release updates the project and package versions to 1.4.0. The changelog documents extraction caching, database error handling, and the corrected reported version. Changes1.4.0 release
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Naseem77
approved these changes
Aug 10, 2026
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.
Cuts the
[Unreleased]section into[1.4.0]and bumps the version. No functional changes — everything released here is already merged onmain.What's in 1.4.0
Chunk-level extraction cache for
update()(#288) —update(..., cache_unchanged_chunks=True)rebuilds untouched chunks from the live graph instead of re-extracting them, so editing one paragraph of a 50-chunk document costs roughly one LLM extraction rather than fifty. Opt-in; the default staysFalse.DatabaseError/DatabaseUnavailableErrorcontract — driver-level failures now surface asDatabaseError, withDatabaseUnavailableErrorseparating "the server never answered" from "the server answered and rejected the query". That split is what lets the cache decide when falling open is safe.Minor bump: purely additive, no breaking changes to existing ingest paths. Callers catching
redis.exceptions.*directly should catchDatabaseErrorinstead — see the Changed section of the changelog.Changes
CHANGELOG.md[Unreleased]→[1.4.0] - 2026-08-10+ summary paragraphgraphrag_sdk/pyproject.toml1.3.0→1.4.0graphrag_sdk/src/graphrag_sdk/__init__.py__version__1.2.0→1.4.0Note on
__version____version__was left at1.2.0when 1.3.0 was cut, so the 1.3.0 release reported a stale version through__version__and the API's/versionendpoint. Fixed here and logged under Fixed. The existingtest_versiononly regex-checks for a1.xshape, which is why it never caught the drift — worth pinning it topyproject.tomlin a follow-up.Not included
IncrementalResolution) — conflicting withmainand has requested changes outstanding; it lands in a later release.🤖 Generated with Claude Code
Summary by CodeRabbit