chore(release): version packages v2.10.2#358
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 20, 2026 16:44
58a7166 to
3f0ea4b
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
rushdb-core@2.10.3
Patch Changes
8e020f2: Dashboard: reworked project Getting Started into a "Connect this project" page with a connection panel (API key, URL, status) and SDK-first setup tabs; neutral, non-shifting feedback for copy/test-connection buttons; unified JSON + language tabs in the Search Query modal.
Core: fixed flaky post-import side effects — record/property counts, schema recalculation, and relationship suggestions could be skipped until records were touched again. Side effects now run on a guaranteed post-commit hook (no polling), with recount → schema recompute → relationship analysis correctly ordered and isolated so one failure no longer cascades.
8e020f2: Make schema recalculation scale with project size and stop AI endpoints from timing out on large datasets
POST /ai/schemaand/ai/schema/mdno longer block or 408 on large projects: a stale cache is served immediately while a single-flight background refresh recomputes it; concurrent requests share one rebuild instead of stacking full-graph scans.force: truestill waits and now guarantees read-your-writes — a force call issued after a write never returns a schema computed before that write committed.POST /ai/search-query) no longer fails with “transaction time budget” errors: the endpoint releases the idle request-scoped transaction before the LLM round-trip (previously the transaction expired while waiting on the LLM and the request failed at commit), and query generation uses the cached schema instead of triggering a synchronous recompute.isArraydetection for string/boolean properties is now based on the bounded sample window (first 100 records per property) rather than a full column scan; number/datetimeisArray, all min/max ranges, record counts, and relationship counts remain exact.rushdb-dashboard@2.10.3
Patch Changes
8e020f2: Dashboard: reworked project Getting Started into a "Connect this project" page with a connection panel (API key, URL, status) and SDK-first setup tabs; neutral, non-shifting feedback for copy/test-connection buttons; unified JSON + language tabs in the Search Query modal.
Core: fixed flaky post-import side effects — record/property counts, schema recalculation, and relationship suggestions could be skipped until records were touched again. Side effects now run on a guaranteed post-commit hook (no polling), with recount → schema recompute → relationship analysis correctly ordered and isolated so one failure no longer cascades.