Skip to content

ci: Version Packages - #2061

Merged
KyleAMathews merged 1 commit into
mainfrom
changeset-release/main
Oct 7, 2026
Merged

KyleAMathews merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

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

@tanstack/angular-db@0.2.6

Patch Changes

@tanstack/browser-db-sqlite-persistence@0.2.31

Patch Changes

  • Updated dependencies []:
    • @tanstack/db-sqlite-persistence-core@0.4.6

@tanstack/capacitor-db-sqlite-persistence@0.2.31

Patch Changes

  • Updated dependencies []:
    • @tanstack/db-sqlite-persistence-core@0.4.6

@tanstack/cloudflare-durable-objects-db-sqlite-persistence@0.2.31

Patch Changes

  • Updated dependencies []:
    • @tanstack/db-sqlite-persistence-core@0.4.6

@tanstack/db@0.12.2

Patch Changes

  • Share duplicated code in direct mutations, index writes, and the query optimizer. The full public API bundle is about 1.4 KB smaller when minified. Errors from a failed BTreeIndex expression now carry the original error as cause, as BasicIndex errors already did. (#2057)

  • Refill an ordered, limited live query over an eager, indexed source in bounded work. Before, deleting a visible row or changing a visible row's order value made the source resend every matching row to the query. For example, a 50-row window over 10,000 rows resent about 5,000 rows on each such change. The query now reads only the first rows of the window from the index, when the query orders by one term. On-demand sources, queries with more than one order term, queries that filter on a LEFT-joined source, and queries that need the whole source (an inner join, a function filter, or a custom collation) keep their existing behavior. (#2055)

  • Fix useLiveInfiniteQuery showing an empty idle result on its first render for a synchronously loaded source. The hook now starts sync during render, as useLiveQuery does, so the first committed render already shows the ready first page instead of flashing empty content before data arrives. This applies to query callbacks and to supplied live query collections whose window is exactly the first page or has no limit. A supplied collection with a wider finite limit waits for the hook to narrow its window at commit, so it never requests rows the hook does not need. Renders that never commit are reclaimed by garbage collection, and a React 19 StrictMode double render reuses one collection instead of starting two. In React, a startup error from a replacement query still reaches the error boundary, and the hook rejects a source replaced by a different collection with the same ID while it is mounted, as useLiveQuery does. (#2027)

  • Place null values first in a descending ordered query that uses an ascending index. Before, the query reversed the index and put rows with a null order value after every non-null row, while the documented order, and the same query without an index, put them first. (#2055)

  • Keep paced mutation persistence serial while a backend write is pending, including after rollback. Preserve every admitted write when managers share one strategy. Reject manual commits that bypass strategy timing. (#2062)
    Restore a transaction's prior optimistic changes when a synchronous mutate callback throws. Reject all receipts in a failed group of paced mutations.

@tanstack/db-sqlite-persistence-core@0.4.6

Patch Changes

@tanstack/electric-db-collection@0.5.7

Patch Changes

@tanstack/electron-db-sqlite-persistence@0.2.7

Patch Changes

  • Updated dependencies []:
    • @tanstack/db-sqlite-persistence-core@0.4.6

@tanstack/expo-db-sqlite-persistence@0.2.31

Patch Changes

  • Updated dependencies []:
    • @tanstack/db-sqlite-persistence-core@0.4.6

@tanstack/indexeddb-db-collection@0.0.4

Patch Changes

@tanstack/node-db-sqlite-persistence@0.2.31

Patch Changes

  • Updated dependencies []:
    • @tanstack/db-sqlite-persistence-core@0.4.6

@tanstack/offline-transactions@1.0.64

Patch Changes

@tanstack/powersync-db-collection@0.2.7

Patch Changes

@tanstack/query-db-collection@1.4.1

Patch Changes

@tanstack/react-db@0.5.6

Patch Changes

  • Fix useLiveInfiniteQuery showing an empty idle result on its first render for a synchronously loaded source. The hook now starts sync during render, as useLiveQuery does, so the first committed render already shows the ready first page instead of flashing empty content before data arrives. This applies to query callbacks and to supplied live query collections whose window is exactly the first page or has no limit. A supplied collection with a wider finite limit waits for the hook to narrow its window at commit, so it never requests rows the hook does not need. Renders that never commit are reclaimed by garbage collection, and a React 19 StrictMode double render reuses one collection instead of starting two. In React, a startup error from a replacement query still reaches the error boundary, and the hook rejects a source replaced by a different collection with the same ID while it is mounted, as useLiveQuery does. (#2027)

  • Updated dependencies [043c9b1, 25201da, 9e8ed99, 25201da, e753bc7]:

    • @tanstack/db@0.12.2

@tanstack/react-native-db-sqlite-persistence@0.2.31

Patch Changes

  • Updated dependencies []:
    • @tanstack/db-sqlite-persistence-core@0.4.6

@tanstack/rxdb-db-collection@0.1.105

Patch Changes

@tanstack/solid-db@0.3.6

Patch Changes

@tanstack/svelte-db@0.5.6

Patch Changes

  • Fix useLiveInfiniteQuery showing an empty idle result on its first render for a synchronously loaded source. The hook now starts sync during render, as useLiveQuery does, so the first committed render already shows the ready first page instead of flashing empty content before data arrives. This applies to query callbacks and to supplied live query collections whose window is exactly the first page or has no limit. A supplied collection with a wider finite limit waits for the hook to narrow its window at commit, so it never requests rows the hook does not need. Renders that never commit are reclaimed by garbage collection, and a React 19 StrictMode double render reuses one collection instead of starting two. In React, a startup error from a replacement query still reaches the error boundary, and the hook rejects a source replaced by a different collection with the same ID while it is mounted, as useLiveQuery does. (#2027)

  • Updated dependencies [043c9b1, 25201da, 9e8ed99, 25201da, e753bc7]:

    • @tanstack/db@0.12.2

@tanstack/tauri-db-sqlite-persistence@0.2.31

Patch Changes

  • Updated dependencies []:
    • @tanstack/db-sqlite-persistence-core@0.4.6

@tanstack/trailbase-db-collection@0.1.117

Patch Changes

@tanstack/vue-db@0.3.6

Patch Changes

@tanstack/capacitor-db-sqlite-persistence-e2e-app@0.0.43

Patch Changes

@tanstack/expo-db-sqlite-persistence-e2e-app@0.0.43

Patch Changes

@tanstack/tauri-db-sqlite-persistence-e2e-app@0.0.43

Patch Changes

@coderabbitai

coderabbitai Bot commented Oct 6, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: ab970685-6998-47c7-97e6-255ee19ad02a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from dd2e13a to 42198fe Compare October 7, 2026 13:47
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 42198fe to 2bb8649 Compare October 7, 2026 16:07
@KyleAMathews
KyleAMathews merged commit c657994 into main Oct 7, 2026
3 checks passed
@KyleAMathews
KyleAMathews deleted the changeset-release/main branch October 7, 2026 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant