-
Notifications
You must be signed in to change notification settings - Fork 145
chore(deps): update all non-major dependencies #987
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
More templates
@tanstack/angular-db
@tanstack/db
@tanstack/db-ivm
@tanstack/electric-db-collection
@tanstack/offline-transactions
@tanstack/powersync-db-collection
@tanstack/query-db-collection
@tanstack/react-db
@tanstack/rxdb-db-collection
@tanstack/solid-db
@tanstack/svelte-db
@tanstack/trailbase-db-collection
@tanstack/vue-db
commit: |
|
Size Change: 0 B Total Size: 89.5 kB ℹ️ View Unchanged
|
|
Size Change: 0 B Total Size: 3.35 kB ℹ️ View Unchanged
|
6aa92b1 to
ae47277
Compare
d6fce5b to
a116f8b
Compare
523189c to
c918905
Compare
c918905 to
372a6de
Compare
This PR contains the following updates:
^1.3.0->^1.3.1^9.39.1->^9.39.2^9.39.1->^9.39.2^9.39.1->^9.39.2^1.43.1->^1.44.0^0.14.3->^0.15.1^1.0.0->^1.1.0^4.1.17->^4.1.18^4.1.17->^4.1.18^4.1.17->^4.1.18^4.1.17->^4.1.18^0.1.37->^0.1.42^0.5.11->^0.5.16^0.2.12->^0.2.20^0.1.1->^0.2.0^1.0.11->^1.0.12^0.1.59->^0.1.60^1.140.0->^1.143.6^1.140.0->^1.143.6^1.140.0->^1.143.6^1.140.0->^1.143.6^1.140.0->^1.143.6^1.140.0->^1.143.6^1.140.0->^1.143.6^0.1.54->^0.1.59^1.140.0->^1.143.6^1.140.0->^1.143.6^0.1.55->^0.1.60^16.3.0->^16.3.1^11.7.2->^11.8.1^8.15.6->^8.16.0^8.15.6->^8.16.0^8.15.6->^8.16.0^8.48.1->^8.50.1^8.48.1->^8.50.1^8.48.1->^8.50.1^8.48.1->^8.50.1^5.1.1->^5.1.2^6.0.2->^6.0.3^2.1.28->^2.1.29^0.45.0->^0.45.1^0.45.0->^0.45.1^9.39.1->^9.39.2^9.39.1->^9.39.2^9.39.1->^9.39.2^0.4.24->^0.4.26^27.2.0->^27.3.0^5.71.0->^5.77.110.24.0->10.26.210.24.0->10.26.2^0.3.15->^0.3.16^19.2.1->^19.2.3^19.2.1->^19.2.3^19.2.1->^19.2.3^19.2.1->^19.2.3^19.2.1->^19.2.3^19.2.1->^19.2.3^5.45.6->^5.46.1^4.3.4->^4.3.5^4.1.17->^4.1.18^4.1.17->^4.1.18^7.2.6->^7.3.0^3.5.25->^3.5.26Release Notes
electric-sql/electric (@electric-sql/client)
v1.3.1Compare Source
Patch Changes
f6e7c75: Fix infinite 409 loop when proxy returns stale cached response with expired shape handle.Root cause: When a 409 response arrives, the client marks the old handle as expired and fetches with a new handle. If a proxy ignores the
expired_handlecache buster parameter and returns a stale cached response containing the old handle, the client would accept it and enter an infinite 409 loop.The fix:
#onInitialResponse: Don't accept a shape handle from the response if it matches the expired handle in the expired shapes cachegetNextChunkUrl(prefetch): Don't prefetch the next chunk if the response handle equals theexpired_handlefrom the request URLThis provides defense-in-depth against misconfigured proxies that don't include all query parameters in their cache keys.
eslint/eslint (@eslint/js)
v9.39.2Compare Source
powersync-ja/powersync-js (@powersync/common)
v1.44.0Compare Source
Minor Changes
299c6dc: Update PowerSync SQLite core to v0.4.10616c2a1: Added ability to specifyappMetadatafor sync/stream requests.Note: This requires a PowerSync service version
>=1.17.0in order for logs to display metadata.standard-schema/standard-schema (@standard-schema/spec)
v1.1.0Compare Source
Adds the Standard JSON Schema specification.
Please refer to the README and standardschema.dev for more details.
tailwindlabs/tailwindcss (@tailwindcss/postcss)
v4.1.18Compare Source
Fixed
source(…)happens relative to the file it is in (#19274)!in the value (#19243)@tailwindcss/vite(#18970)--watch(#19373)ringColor.DEFAULT) in JS configs (#19348)contenttheme key from JS configs (#19381)futureandexperimentalconfig keys (#19344)text-*andleading-*classes (#19396)@keyframes(#19419)/dev/stdout(#19421)TanStack/db (@tanstack/angular-db)
v0.1.42Compare Source
Patch Changes
41308b8]:v0.1.41Compare Source
Patch Changes
32ec4d8]:v0.1.40Compare Source
Patch Changes
26ed0aa]:v0.1.39Compare Source
Patch Changes
8ed7725,01452bf]:v0.1.38Compare Source
Patch Changes
b3b1940,09da081,86ad40c]:TanStack/db (@tanstack/db)
v0.5.16Compare Source
Patch Changes
Fix useLiveInfiniteQuery not updating when deleting an item from a partial page with DESC order. (#970)
The bug occurred when using
useLiveInfiniteQuerywithorderBy(..., 'desc')and having fewer items than thepageSize. Deleting an item would not update the live result - the deleted item would remain visible until another change occurred.The root cause was in
requestLimitedSnapshotwherebiggestObservedValuewas incorrectly set to the full row object instead of the indexed value (e.g., the salary field used for ordering). This caused the BTree comparison to fail, resulting in the same data being loaded multiple times with each item having a multiplicity > 1. When an item was deleted, its multiplicity would decrement but not reach 0, so it remained visible.v0.5.15Compare Source
Patch Changes
fix: prevent duplicate inserts from reaching D2 pipeline in live queries (#1054)
Added defensive measures to prevent duplicate INSERT events from reaching the D2 (differential dataflow) pipeline, which could cause items to not disappear when deleted (due to multiplicity going from 2 to 1 instead of 1 to 0).
Changes:
sentToD2Keystracking inCollectionSubscriberto filter duplicate inserts at the D2 pipeline entry pointincludeInitialStatehandling to only pass whentrue, preventing internal lazy-loading subscriptions from incorrectly disabling filteringsentToD2Keyson truncate to allow re-inserts after collection resetv0.5.14Compare Source
Patch Changes
Fix subscriptions not re-requesting data after truncate in on-demand sync mode. When a must-refetch occurs, subscriptions now buffer changes and re-request their previously loaded subsets, preventing a flash of missing content. (#1043)
Key improvements:
sentKeysis emptyv0.5.13Compare Source
Patch Changes
Allow rows to be deleted by key by using the write function passed to a collection's sync function. (#1003)
fix: deleted items not disappearing from live queries with
.limit()(#1044)Fixed a bug where deleting an item from a live query with
.orderBy()and.limit()would not remove it from the query results. ThesubscribeChangescallback would never fire with a delete event.The issue was caused by duplicate inserts reaching the D2 pipeline, which corrupted the multiplicity tracking used by
TopKWithFractionalIndexOperator. A delete would decrement multiplicity from 2 to 1 instead of 1 to 0, so the item remained visible.Fixed by ensuring
sentKeysis updated before callbacks execute (preventing race conditions) and filtering duplicate inserts infilterAndFlipChanges.v0.5.12Compare Source
Patch Changes
Enhanced LoadSubsetOptions with separate cursor expressions and offset for flexible pagination. (#960)
LoadSubsetOptions.whereno longer includes cursor expressions for pagination. If you have a custom sync layer or query collection that implementsloadSubset, you must now handle pagination separately:cursorproperty (cursor.whereFromandcursor.whereCurrent) and combine them withwhereyourselfoffsetpropertyPreviously, cursor expressions were baked into the
whereclause. Now they are passed separately so sync layers can choose their preferred pagination strategy.Changes:
CursorExpressionstype withwhereFrom,whereCurrent, and optionallastKeypropertiescursortoLoadSubsetOptionsfor cursor-based pagination (separate fromwhere)offsettoLoadSubsetOptionsfor offset-based pagination supportrequestSnapshotcalls when cursor is present:whereCurrent(all ties at boundary, no limit)whereFrom(rows after cursor, with limit)offsetfor query key generationtruncateevent to collections, emitted when synced data is truncated (e.g., aftermust-refetch)setWindowpagination: cursor expressions are now correctly built when paging through resultsloadNextItemsnow passes the correct window offset to prevent incorrect deduplicationCollectionSubscribernow listens fortruncateevents to reset cursor tracking stateBenefits:
where) and pagination (cursor/offset)setWindowcorrectly triggers backend loading for subsequent pages in multi-column orderBy queriesEnsure deterministic iteration order for collections and indexes. (#958)
SortedMap improvements:
compareKeysutility toutils/comparison.tsfor reuseBTreeIndex improvements:
CollectionStateManager changes:
SortedMapforsyncedData, ensuring deterministic iteration ordercomparefunction is provided, entries are sorted by key onlyThis ensures that live queries with
orderByandlimitproduce stable, deterministic results even when multiple rows have equal sort values.Enhanced multi-column orderBy support with lazy loading and composite cursor optimization. (#926)
Changes:
or(gt(col1, v1), and(eq(col1, v1), gt(col2, v2)))) for backend optimizationBenefits:
Updated dependencies [
52c29fa]:TanStack/db (@tanstack/electric-db-collection)
v0.2.20Compare Source
Patch Changes
41308b8]:v0.2.19Compare Source
Patch Changes
Fix slow onInsert awaitMatch performance issue (#1062)
The message buffer was being cleared at the start of each new batch, causing messages to be lost when multiple batches (including heartbeats) arrived before
awaitMatchwas called. This resulted inawaitMatchtiming out (~3-5s per attempt) and transaction rollbacks.The fix removes the buffer clearing between batches. Messages are now preserved until the buffer reaches MAX_BATCH_MESSAGES (1000), at which point the oldest messages are dropped. This ensures
awaitMatchcan find messages even when sync activity arrives before the API call completes.v0.2.18Compare Source
Patch Changes
32ec4d8]:v0.2.17Compare Source
Patch Changes
26ed0aa]:v0.2.16Compare Source
Patch Changes
Adds support for the new subset-end message introduced in Electric. (#1004)
Support tagged rows and move out events in Electric collection. (#942)
Updated dependencies [
8ed7725,01452bf]:v0.2.15Compare Source
Patch Changes
v0.2.14Compare Source
Patch Changes
Fix awaitMatch race condition on inserts and export isChangeMessage/isControlMessage. (#1000)
Bug fixes:
awaitMatchwould timeout on inserts when Electric synced faster than the API callawaitMatchto find thembatchCommittedflag to track commit state, consistent withawaitTxIdsemanticsbatchCommittedto also trigger onsnapshot-endinon-demandmode (matching "ready" semantics)Export fixes:
isChangeMessageandisControlMessageare now exported from the package index as documentedFix invalid Electric proxy queries with missing params for null/undefined values (#951)
When comparison operators were used with null/undefined values, the SQL compiler would generate placeholders ($1, $2) in the WHERE clause but skip adding the params to the dictionary. This resulted in invalid queries being sent to Electric.
Now all comparison operators (eq, gt, lt, gte, lte, like, ilike) throw a clear error when used with null/undefined values, since comparisons with NULL always evaluate to UNKNOWN in SQL. Users should use
isNull()orisUndefined()to check for null values instead.v0.2.13Compare Source
Patch Changes
Enhanced LoadSubsetOptions with separate cursor expressions and offset for flexible pagination. (#960)
LoadSubsetOptions.whereno longer includes cursor expressions for pagination. If you have a custom sync layer or query collection that implementsloadSubset, you must now handle pagination separately:cursorproperty (cursor.whereFromandcursor.whereCurrent) and combine them withwhereyourselfoffsetpropertyPreviously, cursor expressions were baked into the
whereclause. Now they are passed separately so sync layers can choose their preferred pagination strategy.Changes:
CursorExpressionstype withwhereFrom,whereCurrent, and optionallastKeypropertiescursortoLoadSubsetOptionsfor cursor-based pagination (separate fromwhere)offsettoLoadSubsetOptionsfor offset-based pagination supportrequestSnapshotcalls when cursor is present:whereCurrent(all ties at boundary, no limit)whereFrom(rows after cursor, with limit)offsetfor query key generationtruncateevent to collections, emitted when synced data is truncated (e.g., aftermust-refetch)setWindowpagination: cursor expressions are now correctly built when paging through resultsloadNextItemsnow passes the correct window offset to prevent incorrect deduplicationCollectionSubscribernow listens fortruncateevents to reset cursor tracking stateBenefits:
where) and pagination (cursor/offset)setWindowcorrectly triggers backend loading for subsequent pages in multi-column orderBy queriesUpdated dependencies [
b3b1940,09da081,86ad40c]:TanStack/pacer (@tanstack/pacer-lite)
v0.2.0Minor Changes
TanStack/db (@tanstack/query-db-collection)
v1.0.12Compare Source
Patch Changes
41308b8]:TanStack/db (@tanstack/react-db)
v0.1.60Compare Source
Patch Changes
41308b8]:TanStack/router (@tanstack/react-router)
v1.143.6Compare Source
Version 1.143.6 - 12/24/25, 11:22 PM
Changes
Fix
af9ef26) by Manuel SchillerPackages
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.