ci: Version Packages

[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@0.14.0

Minor Changes

• Allow a Query built with Collection descriptors outside a DbClient to bind its sources when a client consumes it. Building or extending a query keeps descriptors unbound until that consumption. A reusable factory descriptor can now serve the same prebuilt query in separate client scopes, including React providers and server preloads. A prepared query is a bound snapshot; reuse the original unbound query across clients. The exported IR now represents an unbound descriptor with DescriptorRef; visitors of IR.From must handle the descriptorRef variant. (#2077)

  React hooks bind standalone descriptor queries through their DbProvider client and report a provider hint when no client is available. Svelte hooks bind through their client and release deferred sources after failed query setup.

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• A direct write (insert, update or delete outside a transaction) whose change subscriber throws no longer leaves a pending transaction behind. Before, the write's transaction stayed pending with its optimistic row visible, its handler never ran, and the Collection kept tracking it. The write now rolls back its own transaction, without rolling back other transactions, and rethrows the subscriber's error. A local-only direct write that takes the fast path (the Collection has no handler for that operation and no other pending or persisting transaction) stores its rows when it publishes them, so it completes its transaction and rethrows. On the transaction path it rolls back and rethrows, as any other direct write does. (#2091)

• Rolling back a transaction that has no mutations no longer causes an unhandled promise rejection. Such a transaction is tracked by no Collection, so nothing else observed its receipt, and Node reported the rejection. Every transaction now marks its receipt as observed when it is created. A caller that reads when('settled') still receives the rejection. (#2104)

• A live query with included child collections now throws when the query graph retires a child collection that still has rows the graph never removed. The graph always removes a child collection's rows before it retires it, so this is an internal invariant violation. Before, the rows were removed silently, which hid the fault. The failed flush restores the child collections, as for any failed flush. (#2092)

  Calling cleanup() on a child collection of a live query now returns a rejected promise. The live query owns its child collections, and several parent rows can share one. Before, a cleanup stopped the child collection for every parent that shared it, so they never saw its rows again. Clean up the live query instead. Ordinary Collections are not affected.

  An optimistic update of a row in a child collection no longer throws "Bucket facade row has no public key". Each child row now carries its key in $key, so the copy that an update makes keeps it.

  Also fix a lost child row behind a persisting transaction. When a user transaction on a child collection was persisting, an update to a child row that an earlier flush had written was applied as a delete, so the row disappeared when the transaction settled. A rollback in that state could also delete such a row. The adapter now decides each write from the child collection's synced rows, including writes that a persisting transaction holds, not from the rows the child collection shows.

• A live query over a progressive Electric collection is now ready once its own snapshot loads. Before, it stayed loading until the collection's background full sync completed, so preload(), isReady, and useLiveSuspenseQuery waited for the whole dataset even when the query's rows were already present. A live query now waits for an eager source to be ready and for an on-demand source's subset loads to settle. An on-demand source's own readiness no longer gates the query. (#2115)

  An effect with skipInitial: true ends its initial suppression at the same point. Before, an effect over an on-demand source that was already ready reported its initial rows as enter events.

  A live query no longer enters an error state when a truncate of a lazily loaded source (a joined or included collection) aborts that source's pending load during the initial load. The truncate's replacement load now decides the demand.

  A progressive Electric load that arrives while a must-refetch is replacing the initial snapshot now settles when the replacement completes. Before, it settled at once without loading rows, which the new readiness rule would have reported as a ready, empty query. After a stream error that onError retries, later progressive loads settle once the stream recovers.

  toArrayWhenReady() and stateWhenReady() now resolve when preload() does. Before, they resolved as soon as the collection held any row, so on a live query they could resolve before the query was ready.

• An aggregate query without groupBy no longer drops its other select fields silently. Inside an include, a literal or a parent field now appears beside the aggregate, for example { n: count(c.id), px: issue.x }. Before, px was undefined. A field of the query's own source has no single value for the group, so it now throws NonAggregateExpressionNotInGroupByError, as it already did with groupBy. Before, it was undefined. This also applies to a source field outside the aggregates of a wrapped, conditional or nested value, such as add(count(c.id), c.v), and to a spread such as { ...c, n: count(c.id) }. Aggregate the field (for example with max) or add it to groupBy. (#2094)

  With groupBy, a literal or a parent field beside the aggregate is now accepted and published, because it has one value per group. Before, it threw. A nested include in a grouped or aggregate select now throws. Before, it was null without groupBy.

  A HAVING condition that compares a group key, such as having(({ c }) => eq(c.k, 'a')), now keeps the matching groups. Before, it removed every group. A HAVING condition that reads another source field outside an aggregate now throws NonAggregateExpressionNotInGroupByError. Before, it removed every group. A grouped select that repeats a groupBy expression with an array, Date or NaN literal no longer throws, and a parent field is accepted when the include's source reuses the parent's alias. The error message no longer says "in SELECT", because it also applies to HAVING. An aggregate query without groupBy whose select only wraps its aggregate, such as { n: add(count(c.id), 1) }, now accepts HAVING on its selected values, parent fields and literals. Before, it threw HavingRequiresGroupByError. An aggregate inside HAVING must still be a top-level select field. The same rule applies after unionAll: a field of the union's rows outside an aggregate throws. A grouped row keeps the select's field order.

• Keep ordered snapshots from resending rows already delivered by full-state or skip-filtering subscriptions. Release deleted keys from snapshot tracking. Preserve provider coverage when pending optimistic changes hide rows or change an ordered window. (#2086)

• Reject reuse of mutable persisted and LocalStorage sync options across Collections while keeping DbClient materializations independent. Pass fresh options to each direct createCollection(...); DbClient descriptors remain reusable. Keep on-demand peer reloads and schema resets scoped to active demand and previously visible rows. Refresh or delete visible rows from durable evidence without replacing unconfirmed DbClient hydration rows or metadata. Resolve targeted peer updates from storage when their notice cannot distinguish a replacing insert from a partial update. (#2096)

• Preserve lexical source bindings when a correlated right or full join has an absent side, and allow captured ancestor references in join conditions. (#2095)

• Aggregate queries hydrate and update faster. groupBy merges equal contributions to a group, and it used to find them by hashing every contribution. Each contribution now leads with an identity string built from its group key and its pre-aggregate values, and the reduce index merges contributions with equal identities without hashing them. D2 value identity (equalHashValues) defines the identity: two values get the same identity string exactly when D2 treats them as equal. Primitives, arrays, plain and class-instance objects, Dates, RegExps, Maps, Sets and Uint8Arrays get an identity. A contribution that holds anything else, a value nested more than four levels deep, or an object with an enumerable symbol key still goes through the structural hash. A grouped count or min over 10,000 rows hydrates about 2× faster. (#2112)

• Live queries with includes hydrate faster. The rows that the include graph keeps in its join and reduce state now lead with their key, so the dataflow index tells them apart by key and hashes a whole row only to match it against a row with the same key, such as its own retraction. On a 10,000-issue benchmark, an issue-to-creator include hydrates about 30% faster and a two-level include about 33% faster. (#2109)

• Updated dependencies [cf07eec, be4a3d6]:

  • @tanstack/db-ivm@0.1.27

@tanstack/angular-db@0.2.9

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0

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

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• Updated dependencies [cda9d6a, 6fa60aa]:

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

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

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• Updated dependencies [cda9d6a, 6fa60aa]:

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

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

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• Updated dependencies [cda9d6a, 6fa60aa]:

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

@tanstack/db-ivm@0.1.27

Patch Changes

• Structural hashing now gives equal objects the same hash when two of their keys are distinct strings that locale collation ranks as equal, such as a precomposed Å and A followed by a combining ring. Before, the hash sorted keys with localeCompare, so the hash of such an object depended on the order its keys were inserted, and two equal rows could fail to consolidate in a live query. Keys now sort by UTF-16 code unit, which is a total order. This changes the digest of objects whose keys sort differently by code unit than by locale, for example { a: 1, B: 2 }. Digests are per process, so no stored value depends on them. Hashing also writes whole 32-bit words to the hash stream, which makes hashing rows faster. The stream still hashes the same bytes. (#2108)

• Aggregate queries hydrate and update faster. groupBy merges equal contributions to a group, and it used to find them by hashing every contribution. Each contribution now leads with an identity string built from its group key and its pre-aggregate values, and the reduce index merges contributions with equal identities without hashing them. D2 value identity (equalHashValues) defines the identity: two values get the same identity string exactly when D2 treats them as equal. Primitives, arrays, plain and class-instance objects, Dates, RegExps, Maps, Sets and Uint8Arrays get an identity. A contribution that holds anything else, a value nested more than four levels deep, or an object with an enumerable symbol key still goes through the structural hash. A grouped count or min over 10,000 rows hydrates about 2× faster. (#2112)

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

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• Reject reuse of mutable persisted and LocalStorage sync options across Collections while keeping DbClient materializations independent. Pass fresh options to each direct createCollection(...); DbClient descriptors remain reusable. Keep on-demand peer reloads and schema resets scoped to active demand and previously visible rows. Refresh or delete visible rows from durable evidence without replacing unconfirmed DbClient hydration rows or metadata. Resolve targeted peer updates from storage when their notice cannot distinguish a replacing insert from a partial update. (#2096)

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:

  • @tanstack/db@0.14.0

@tanstack/electric-db-collection@0.5.10

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• A live query over a progressive Electric collection is now ready once its own snapshot loads. Before, it stayed loading until the collection's background full sync completed, so preload(), isReady, and useLiveSuspenseQuery waited for the whole dataset even when the query's rows were already present. A live query now waits for an eager source to be ready and for an on-demand source's subset loads to settle. An on-demand source's own readiness no longer gates the query. (#2115)

  An effect with skipInitial: true ends its initial suppression at the same point. Before, an effect over an on-demand source that was already ready reported its initial rows as enter events.

  A live query no longer enters an error state when a truncate of a lazily loaded source (a joined or included collection) aborts that source's pending load during the initial load. The truncate's replacement load now decides the demand.

  A progressive Electric load that arrives while a must-refetch is replacing the initial snapshot now settles when the replacement completes. Before, it settled at once without loading rows, which the new readiness rule would have reported as a ready, empty query. After a stream error that onError retries, later progressive loads settle once the stream recovers.

  toArrayWhenReady() and stateWhenReady() now resolve when preload() does. Before, they resolved as soon as the collection held any row, so on a live query they could resolve before the query was ready.

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:

  • @tanstack/db@0.14.0

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

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• Updated dependencies [cda9d6a, 6fa60aa]:

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

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

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• Updated dependencies [cda9d6a, 6fa60aa]:

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

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

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• Updated dependencies [cda9d6a, 6fa60aa]:

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

@tanstack/offline-transactions@1.1.1

Patch Changes

• A failed auto-commit of an offline transaction no longer causes an unhandled promise rejection. mutate() with autoCommit (the default) committed through its own copy of the auto-commit logic, which logged the failure and then rethrew it inside a .catch, so every failed auto-commit reached unhandledRejection. The offline transaction now passes autoCommit to its TanStack DB transaction, which reports the failure through when('settled') without an unhandled rejection. The extra Auto-commit failed: console error is gone. (#2090)

  createOfflineAction also commits through the TanStack DB auto-commit and no longer prints debug messages (createOfflineAction 2, mutate, offlineAction committed) to the console.

• waitForTransactionCompletion now settles for an offline transaction whose mutate() callback writes nothing. Such a transaction completes without running its mutation function, so before this change the executor never settled its waiter, and the promise stayed pending forever. It also settles for a transaction that is rolled back before it commits: the waiter rejects with the rollback's error, or with an Error that names the rollback when rollback() gives none. A transaction rolled back while it persists still reports the executor's outcome. A callback that throws still leaves its transaction pending, as a core transaction does, so its waiter also stays pending until the transaction commits. (#2100)

  On a tab without offline leadership, createOfflineTransaction returns a plain transaction that the executor does not track, so waitForTransactionCompletion does not apply there.

• waitForTransactionCompletion(id) no longer waits forever for a transaction that the executor already settled. Such a waiter now rejects with an error that says the transaction already settled. The executor remembers the last 1,000 transactions it settled. A waiter for an id that the executor does not know yet keeps waiting, because another tab can still queue that transaction. (#2105)

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:

  • @tanstack/db@0.14.0

@tanstack/powersync-db-collection@0.2.10

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0

@tanstack/query-db-collection@1.4.4

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• Prevent direct writes from automatically refetching active Query subsets. On-demand writes patch changed keys already present in active raw arrays or directly selected response arrays, except when the Query is shared with another Collection. Eager writes patch representable rows in a shared Query cache, so Collections using the same Query project those edits. In both modes, cache patches preserve Query error, invalidation, and freshness state; an idle eager cache seed moves from pending to success without advancing its freshness timestamp. Direct writes no longer clear a prior fetch error or mark stale data fresh. Older in-flight or queued results cannot undo an accepted write, and derived cache responses are not replayed over it on resubscribe. A later-started successful subset fetch controls a shared row's value over an older request that settles afterward. Callers choose when to request current server rows; a complete matching on-demand result can remove an omitted ownerless direct row. Query Core 5.90.15 or later is required for post-write refetch replacement and error-state recovery. (#2065)

  An eager Collection that later joins a Query patched by another eager Collection projects the cached edit without starting a request, including when disabled. An on-demand Collection still revalidates an unverified cache edit before accepting it for a subset. A fresh persisted Collection refetches on a cached-row collision when it cannot recover the order of its stored direct write and that Query result.
  Inactive Query entries under the Collection key prefix may be removed after a direct write. A physical Query whose stored key is outside that prefix remains in the cache, even when a custom hash aliases it with a Collection key; callers can explicitly evict or refetch that entry.

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:

  • @tanstack/db@0.14.0

@tanstack/react-db@0.5.9

Patch Changes

• Allow a Query built with Collection descriptors outside a DbClient to bind its sources when a client consumes it. Building or extending a query keeps descriptors unbound until that consumption. A reusable factory descriptor can now serve the same prebuilt query in separate client scopes, including React providers and server preloads. A prepared query is a bound snapshot; reuse the original unbound query across clients. The exported IR now represents an unbound descriptor with DescriptorRef; visitors of IR.From must handle the descriptorRef variant. (#2077)

  React hooks bind standalone descriptor queries through their DbProvider client and report a provider hint when no client is available. Svelte hooks bind through their client and release deferred sources after failed query setup.

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:

  • @tanstack/db@0.14.0

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

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• Updated dependencies [cda9d6a, 6fa60aa]:

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

@tanstack/rxdb-db-collection@0.1.108

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0

@tanstack/solid-db@0.3.9

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0

@tanstack/svelte-db@0.5.9

Patch Changes

• Allow a Query built with Collection descriptors outside a DbClient to bind its sources when a client consumes it. Building or extending a query keeps descriptors unbound until that consumption. A reusable factory descriptor can now serve the same prebuilt query in separate client scopes, including React providers and server preloads. A prepared query is a bound snapshot; reuse the original unbound query across clients. The exported IR now represents an unbound descriptor with DescriptorRef; visitors of IR.From must handle the descriptorRef variant. (#2077)

  React hooks bind standalone descriptor queries through their DbProvider client and report a provider hint when no client is available. Svelte hooks bind through their client and release deferred sources after failed query setup.

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:

  • @tanstack/db@0.14.0

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

Patch Changes

• Recover persisted on-demand Electric and Query collections after cache claim loss by rotating their SQLite cache and reloading active subsets. Fence retired provider work and expired claims, preserve warm runs on their claimed cache generation, and forward claim lifetime options through SQLite host factories. Require explicit eager or claim-bound managed targets for SQLite adapter data operations, and forward them through Electron IPC protocol v6. Bare collection IDs no longer work at this lower-level adapter boundary. (#2069)

• Updated dependencies [cda9d6a, 6fa60aa]:

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

@tanstack/trailbase-db-collection@0.1.120

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0

@tanstack/vue-db@0.3.9

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0

todos@0.0.26

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0
  • @tanstack/angular-db@0.2.9

offline-transactions-react-native@1.0.13

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, 9b17253, d83b6cd, cd63c6c, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, d0dfcda, fd13e3c]:
  • @tanstack/db@0.14.0
  • @tanstack/query-db-collection@1.4.4
  • @tanstack/react-native-db-sqlite-persistence@0.2.34
  • @tanstack/offline-transactions@1.1.1
  • @tanstack/react-db@0.5.9

shopping-list-react-native@1.0.13

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, 9b17253, d83b6cd, cd63c6c, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0
  • @tanstack/electric-db-collection@0.5.10
  • @tanstack/react-native-db-sqlite-persistence@0.2.34
  • @tanstack/offline-transactions@1.1.1
  • @tanstack/react-db@0.5.9

@tanstack/db-example-react-next-ssr-e2e@0.0.8

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0
  • @tanstack/react-db@0.5.9

@tanstack/db-example-paced-mutations-demo@0.0.18

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0
  • @tanstack/react-db@0.5.9

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

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0
  • @tanstack/capacitor-db-sqlite-persistence@0.2.34

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

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0
  • @tanstack/expo-db-sqlite-persistence@0.2.34

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

Patch Changes

• Updated dependencies [cda9d6a, dfec42e, 1a65c2c, 1b4ee8d, bc6f30e, bbe9327, b34a579, 6fa60aa, f84387c, be4a3d6, 0dc696a, fd13e3c]:
  • @tanstack/db@0.14.0
  • @tanstack/tauri-db-sqlite-persistence@0.2.34

[coderabbitai]

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: 7ea83b6a-5202-4d0c-995d-e5e2e50d97c2

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.}