[github-actions]

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/db-sqlite-persistence-core@0.5.0

Minor Changes

• Reloaded persisted collections now read their rows before they write a leader election term. A collection still takes its leader lock when it subscribes, but it reserves its durable term only after the database work already queued on the shared scheduler has settled, or as soon as something needs a leader during that election: a local write, a follower request, a sync commit during startup, or ensureLeadership. A need that an earlier leader already served does not let a later takeover skip the wait. A tab that takes over treats the departed leader's route as gone, so a sync commit queued behind one of its reads goes to the new leader and settles without waiting out an RPC timeout. The Electron renderer applies the same rule to its own hydrations. The renderer now has a hydration scope, so its startup runs as one hydration, as a Browser tab's does, and a restart keeps its metadata and row reads in one scope, so a term cannot run between them. (#2219)

  ensureLeadership now resolves when this node becomes leader, keeps its place in the Web Locks queue instead of replacing its lock request, and rejects if the coordinator is disposed.

  Migration for custom persistence adapters: runInRegularScope is now a RegularScope, which must also provide afterQueuedWork(). It resolves once every operation queued or running on the adapter's scheduler at the call has settled. An adapter without a scheduler can return a promise that settles with its running hydrations. A coordinator now rejects an adapter whose runInRegularScope lacks afterQueuedWork with InvalidPersistenceAdapterError.

Patch Changes

• Apps without a persisted Collection no longer bundle the persisted initial-render wait. The persistence adapter now supplies the wait, so a typical app is about 230 bytes smaller after gzip. (#2228)

• Reloads no longer repeat setup that is already complete. A reopened persisted collection checks its tables, indexes, triggers, and bookkeeping rows in the same query that reads its registration, and runs its nine setup statements only when something is missing. Each adapter checks database-wide setup with one query and runs it only when a table, index, or migrated column is missing, instead of about 19 statements on every load. The write-only global schema_version row, which adapters with different schema versions overwrote on every load, is no longer created or written. (#2219)

  A tab no longer rereads all of a collection's rows after its own write. It used to record the write's stream position before that write's commit notice arrived, so the notice looked like a gap and triggered pullSince and a full row scan.

• Add SQLiteConnectionClosedError. A browser OPFS connection now rejects requests made after close starts with this error instead of InvalidPersistedCollectionConfigError. (#2213)

• Updated dependencies [30175be, 37b8fc2]:

  • @tanstack/db@0.15.3

@tanstack/angular-db@0.2.13

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3

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

Patch Changes

• Add SQLiteConnectionClosedError. A browser OPFS connection now rejects requests made after close starts with this error instead of InvalidPersistedCollectionConfigError. (#2213)

• Reject pending OPFS requests when closing the SQLite connection, including when the worker reports a close error. Close now stops accepting requests when it starts, and concurrent close() calls share one outcome. The OPFS worker handles one request at a time, so close waits for earlier queries instead of failing while one waits for the OPFS access handle. (#2213)

• Updated dependencies [205ab71, 37b8fc2, 205ab71, b052e91]:

  • @tanstack/db-sqlite-persistence-core@0.5.0

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

Patch Changes

• Updated dependencies [205ab71, 37b8fc2, 205ab71, b052e91]:
  • @tanstack/db-sqlite-persistence-core@0.5.0

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

Patch Changes

• Updated dependencies [205ab71, 37b8fc2, 205ab71, b052e91]:
  • @tanstack/db-sqlite-persistence-core@0.5.0

@tanstack/db@0.15.3

Patch Changes

• Keep ordered live queries accurate and loading when source work overlaps. A window with orderBy and limit no longer stops loading, keeps old rows, or holds acquisitions in these cases: a failed or superseded request, a truncate replay, a source change during a repair, or an on-demand joined source. Recovery after a failure uses one full-source read, and a window move whose load succeeded now resolves. (#2194)

  When an adapter's unloadSubset throws, TanStack DB now reports the error as an uncaught error and continues as if the release succeeded. The error is no longer a subset failure. It does not set lastError or lastSubsetError, fail a truncate replay, reject setWindow(), or dispose an Effect. unsubscribe(), releaseSnapshot(), and Effect dispose() no longer throw or reject with it.

  The newest setWindow() call now wins. A pending source recovery that defers two calls no longer lets the older one set the window. A superseded call that succeeds now resolves only after the newest call settles, so awaiting it shows the window that won.

• Apps without a persisted Collection no longer bundle the persisted initial-render wait. The persistence adapter now supplies the wait, so a typical app is about 230 bytes smaller after gzip. (#2228)

@tanstack/electric-db-collection@0.6.4

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3

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

Patch Changes

• Reloaded persisted collections now read their rows before they write a leader election term. A collection still takes its leader lock when it subscribes, but it reserves its durable term only after the database work already queued on the shared scheduler has settled, or as soon as something needs a leader during that election: a local write, a follower request, a sync commit during startup, or ensureLeadership. A need that an earlier leader already served does not let a later takeover skip the wait. A tab that takes over treats the departed leader's route as gone, so a sync commit queued behind one of its reads goes to the new leader and settles without waiting out an RPC timeout. The Electron renderer applies the same rule to its own hydrations. The renderer now has a hydration scope, so its startup runs as one hydration, as a Browser tab's does, and a restart keeps its metadata and row reads in one scope, so a term cannot run between them. (#2219)

  ensureLeadership now resolves when this node becomes leader, keeps its place in the Web Locks queue instead of replacing its lock request, and rejects if the coordinator is disposed.

  Migration for custom persistence adapters: runInRegularScope is now a RegularScope, which must also provide afterQueuedWork(). It resolves once every operation queued or running on the adapter's scheduler at the call has settled. An adapter without a scheduler can return a promise that settles with its running hydrations. A coordinator now rejects an adapter whose runInRegularScope lacks afterQueuedWork with InvalidPersistenceAdapterError.

• Updated dependencies [205ab71, 37b8fc2, 205ab71, b052e91]:

  • @tanstack/db-sqlite-persistence-core@0.5.0

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

Patch Changes

• Updated dependencies [205ab71, 37b8fc2, 205ab71, b052e91]:
  • @tanstack/db-sqlite-persistence-core@0.5.0

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

Patch Changes

• Updated dependencies [205ab71, 37b8fc2, 205ab71, b052e91]:
  • @tanstack/db-sqlite-persistence-core@0.5.0

@tanstack/offline-transactions@1.1.5

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3

@tanstack/powersync-db-collection@0.2.14

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3

@tanstack/query-db-collection@1.4.9

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3

@tanstack/react-db@0.5.13

Patch Changes

• Production builds no longer include the development warnings of useLiveQuery. A typical app's bundle is about 1.6 kB smaller before compression and 0.66 kB smaller after gzip. (#2227)

• Updated dependencies [30175be, 37b8fc2]:

  • @tanstack/db@0.15.3

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

Patch Changes

• Updated dependencies [205ab71, 37b8fc2, 205ab71, b052e91]:
  • @tanstack/db-sqlite-persistence-core@0.5.0

@tanstack/rxdb-db-collection@0.1.112

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3

@tanstack/solid-db@0.3.13

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3

@tanstack/svelte-db@0.5.13

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3

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

Patch Changes

• Updated dependencies [205ab71, 37b8fc2, 205ab71, b052e91]:
  • @tanstack/db-sqlite-persistence-core@0.5.0

@tanstack/trailbase-db-collection@0.1.124

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3

@tanstack/vue-db@0.3.13

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3

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

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3
  • @tanstack/capacitor-db-sqlite-persistence@0.2.38

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

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3
  • @tanstack/expo-db-sqlite-persistence@0.2.38

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

Patch Changes

• Updated dependencies [30175be, 37b8fc2]:
  • @tanstack/db@0.15.3
  • @tanstack/tauri-db-sqlite-persistence@0.2.38

[coderabbitai]

Important

Review skipped

Bot user detected.

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

⚙️ Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 93adc72d-1b64-48ad-a121-a6b3c1bc328d

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

• Autofix · 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

• X
• Mastodon
• Reddit
• LinkedIn

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