ci: Version Packages#1621
Merged
Merged
Conversation
bd25e6a to
b00f365
Compare
b00f365 to
dbe3ea6
Compare
More templates
@tanstack/angular-db
@tanstack/browser-db-sqlite-persistence
@tanstack/capacitor-db-sqlite-persistence
@tanstack/cloudflare-durable-objects-db-sqlite-persistence
@tanstack/db
@tanstack/db-ivm
@tanstack/db-sqlite-persistence-core
@tanstack/electric-db-collection
@tanstack/electron-db-sqlite-persistence
@tanstack/expo-db-sqlite-persistence
@tanstack/node-db-sqlite-persistence
@tanstack/offline-transactions
@tanstack/powersync-db-collection
@tanstack/query-db-collection
@tanstack/react-db
@tanstack/react-native-db-sqlite-persistence
@tanstack/rxdb-db-collection
@tanstack/solid-db
@tanstack/svelte-db
@tanstack/tauri-db-sqlite-persistence
@tanstack/trailbase-db-collection
@tanstack/vue-db
commit: |
Contributor
Author
|
Size Change: 0 B Total Size: 124 kB ℹ️ View Unchanged
|
Contributor
Author
|
Size Change: 0 B Total Size: 4.26 kB ℹ️ View Unchanged
|
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
@tanstack/angular-db@0.1.71
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/browser-db-sqlite-persistence@0.2.3
Patch Changes
@tanstack/capacitor-db-sqlite-persistence@0.2.3
Patch Changes
@tanstack/cloudflare-durable-objects-db-sqlite-persistence@0.2.3
Patch Changes
@tanstack/db@0.6.11
Patch Changes
Fix incorrect results from index-optimized
whereclauses that combine indexed and non-indexed conditions. (#1582)ORexpressions are now only served from indexes when every disjunct can use an index; otherwise the query falls back to a full scan. Previously, rows matched only by a non-indexed disjunct were missing from the result.ANDexpressions still use indexes for the conditions that have them, but the remaining conditions are now enforced by re-checking each candidate row against the full expression. Previously, non-indexed conditions were silently dropped, returning rows that did not match the query.age > 5 AND age < 10) combined with conditions on other fields no longer ignore those other conditions.age >= 5 AND age > 5) now apply the strictest bound regardless of the order the conditions appear in, using the same value comparison semantics as the indexes (dates, locale strings, ...).age > 5 AND age >= 8) no longer return an empty result.gt/lt) on BTree-indexed fields holding normalized values such as dates now correctly exclude the boundary value.null/undefinedbound (e.g.gt(score, undefined)) now re-filter against the full expression instead of returning index-ordered rows, matching the semantics of a full scan (a comparison againstnull/undefinedis never true).eq,IN, and range queries on a field that has rows withnull/undefinedvalues no longer leak those rows into results. BTree indexes store and return such rows (they sort as the smallest key), but a comparison againstnull/undefinedis never true, so these results are now re-filtered against the full expression to stay equivalent to a full scan.gt/gte/lt/lte) on a collection using locale string collation (the default) are no longer served by the index. The index orders strings withlocaleComparewhile thewhereevaluator compares them with standard relational operators, so an index range lookup could omit matching rows; these conditions now fall back to a full scan.whereevaluator (arrays, plain objects, Temporal values) now fall back to a full scan instead of using the index, which could otherwise omit matching rows.whereevaluator's relational operators.fix(query): drive lazy-join loading through the collection the join key resolves to (#1614)
When a subquery used in a JOIN clause selects its join key from a joined source rather than from its own
fromclause, the lazy-join loader subscribed to the wrong inner source: it used the subquery'sfromalias while computing the index requirement against the collection the key actually resolves to. This produced a misleadingJoin requires an indexwarning naming an already-indexed collection and an unnecessary full-load fallback.followRefnow reports the resolved source alias, so lazy loading subscribes to the correct collection and loads through its index.Adopt PostgreSQL float semantics for
NaNinwhereclauses and ordering. (#1582)NaN(and invalidDatevalues, whose timestamp isNaN) previously had no consistent order —NaN === NaNisfalsein JavaScript, soNaNcompared unequal to everything and could not be sorted or indexed deterministically. Following PostgreSQL,NaNis now treated as equal to itself and greater than every other non-null value:eq(row.value, NaN)matches rows whose value isNaN;inArray(row.value, [NaN, ...])matches them too.NaNas the greatest value:gt/gteinclude it,lt/lteexclude it.NaNis now deterministic, withNaNsorting last (andnullstill ordered byNULLS FIRST/NULLS LAST).null/undefinedare unaffected: they continue to use three-valued logic (a comparison withnullyieldsUNKNOWN).This makes results independent of whether a query is served from an index or a full scan.
Fix prototype pollution via
select()alias paths. Aliases were split on.and walked into the result object without sanitization, so a query likeselect(() => ({ ['__proto__.polluted']: ... }))(or any segment matching__proto__,prototype, orconstructor) could mutateObject.prototype. The select compiler now rejects unsafe alias path segments with a newUnsafeAliasPathError. Fixes Prototype Pollution viaqueryOnce().select()Alias Handling #1584. (#1595)@tanstack/db-sqlite-persistence-core@0.2.3
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/electric-db-collection@0.3.9
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/electron-db-sqlite-persistence@0.1.15
Patch Changes
@tanstack/expo-db-sqlite-persistence@0.2.3
Patch Changes
@tanstack/node-db-sqlite-persistence@0.2.3
Patch Changes
@tanstack/offline-transactions@1.0.36
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/powersync-db-collection@0.1.49
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/query-db-collection@1.0.43
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/react-db@0.1.89
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/react-native-db-sqlite-persistence@0.2.3
Patch Changes
@tanstack/rxdb-db-collection@0.1.77
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/solid-db@0.2.25
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/svelte-db@0.1.88
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/tauri-db-sqlite-persistence@0.2.3
Patch Changes
@tanstack/trailbase-db-collection@0.1.89
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/vue-db@0.0.122
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/capacitor-db-sqlite-persistence-e2e-app@0.0.15
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/expo-db-sqlite-persistence-e2e-app@0.0.15
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]:@tanstack/tauri-db-sqlite-persistence-e2e-app@0.0.15
Patch Changes
d79b0cd,36fb29a,d79b0cd,ac09b11]: