ci: Version Packages #1079
Open
ci: Version Packages #1079
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
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
a875556 to
74c838e
Compare
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
Fix orphan transactions after
must-refetchin progressive sync mode (#1069)When a
must-refetchmessage was received in progressive mode, it started a transaction withtruncate()but resethasReceivedUpToDate, causing subsequent messages to be buffered instead of written to the existing transaction. Onup-to-date, the atomic swap code would create a new transaction, leaving the first one uncommitted forever. This caused collections to become corrupted with undefined values.The fix ensures that when a transaction is already started (e.g., from must-refetch), messages are written directly to it instead of being buffered for atomic swap.
Fix duplicate key error when overlapping subset queries return the same row with different values. (#1070)
When multiple subset queries return the same row (e.g., different WHERE clauses that both match the same record), the server sends
insertoperations for each response. If the row's data changed between requests (e.g., timestamp field updated), this caused aDuplicateKeySyncError. The adapter now tracks synced keys and converts subsequent inserts to updates.