ci: Version Packages #1067
Merged
ci: Version Packages #1067
Conversation
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/[email protected]
Patch Changes
41308b8]:@tanstack/[email protected]
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.@tanstack/[email protected]
Patch Changes
41308b8]:@tanstack/[email protected]
Patch Changes
41308b8]:@tanstack/[email protected]
Patch Changes
41308b8]:@tanstack/[email protected]
Patch Changes
41308b8]:@tanstack/[email protected]
Patch Changes
41308b8]:@tanstack/[email protected]
Patch Changes
41308b8]:@tanstack/[email protected]
Patch Changes
41308b8]:@tanstack/[email protected]
Patch Changes
41308b8]:@tanstack/[email protected]
Patch Changes
41308b8]:@tanstack/[email protected]
Patch Changes
41308b8]: