Repository navigation
ci: Version Packages - #1323
Merged
Merged
ci: Version Packages#1323
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
October 15, 2026 07:07
211fb79 to
35a3782
Compare
Contributor
Author
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
|
View your CI Pipeline Execution ↗ for commit f44a5f6
☁️ Nx Cloud last updated this comment at |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
October 15, 2026 12:39
aaebcab to
582d3dd
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 15, 2026 13:21
582d3dd to
f44a5f6
Compare
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
1 participant
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-virtual@6.1.6
Patch Changes
56b2a63,d2c7911,9c762fe,6789f7a,77cb05e,4a1a4fd,3c61b6e,9c762fe]:@tanstack/lit-virtual@3.14.9
Patch Changes
56b2a63,d2c7911,9c762fe,6789f7a,77cb05e,4a1a4fd,3c61b6e,9c762fe]:@tanstack/marko-virtual@3.16.6
Patch Changes
56b2a63,d2c7911,9c762fe,6789f7a,77cb05e,4a1a4fd,3c61b6e,9c762fe]:@tanstack/react-virtual@3.14.20
Patch Changes
56b2a63,d2c7911,9c762fe,6789f7a,77cb05e,4a1a4fd,3c61b6e,9c762fe]:@tanstack/solid-virtual@3.13.47
Patch Changes
56b2a63,d2c7911,9c762fe,6789f7a,77cb05e,4a1a4fd,3c61b6e,9c762fe]:@tanstack/svelte-virtual@3.13.46
Patch Changes
56b2a63,d2c7911,9c762fe,6789f7a,77cb05e,4a1a4fd,3c61b6e,9c762fe]:@tanstack/virtual-core@3.19.5
Patch Changes
#1330
56b2a63- fix(virtual-core): keep an instant scroll command clamped at a max the sizer committed outside a row resizeBefore an instant scroll command's write is reported, the browser can clamp it at a smaller scroll max that the sizer moves to without a row resize: an append or prepend,
measure(), or a resize the sizer had not committed when the command was written. The virtualizer now also records the max at each commit, so such an event is read as its own clamped write and the command lands. A clamped write reported withisScrollingfalse is now written again too.#1329
d2c7911- fix(virtual-core): keep an instant scroll command when the browser clamps its write before rows grow backRows measured right after an instant
scrollToEnd()(orscrollToIndex) can first shrink the sizer below the written position and then grow it again in the same task. The browser clamps the write to the smaller max, and the scroll event reports that position. It was read as the user scrolling away, so the command was cancelled and the list stopped short of the end (a chat opened withestimateSizelarger than its rows). The virtualizer now follows the scroll max through those measurements and reads such an event as its own clamped write, so the command retargets and lands at the end.#1324
9c762fe- fix(virtual-core): scroll commands and corrections that stalled or were lost (#1307)scrollTopwrite no longer stops a fling but is overridden by it within a frame. AscrollToIndex,scrollToOffsetorscrollToEndissued during a fling now waits for the fling to end instead of being lost. The user taking over before then cancels it: a drag, a second flick, or a finger stopping the fling (iOS reports none of these with touch events while the fling runs). Corrections keep being held through the gesture as on every version.scrollToOffset/scrollBy: a row above the viewport growing after the write's read-back moved the element off the fixed target, and the command kept reconciling until the 5s safety valve. The target now moves with the correction.anchorTo: 'end') before the read-back of a scroll command was anchored against the stale offset and written over the command. It is now left to reconcile, like a resize in that window.#1332
6789f7a- fix(virtual-core): on iOS 27 and later, a scroll command issued during a fling takes effect at onceA
scrollToIndex,scrollToOffsetorscrollToEndissued during a fling waited for the fling to end, so a button outside the list (such as "jump to latest") did nothing until the list stopped. The command now stops the fling by hiding the scroll element's overflow for two frames, then restores the element's own inline value and writes. The user taking over before the write still cancels the command.#1325
77cb05e- refactor(virtual-core): move the iOS touch gesture tracking into its own internal module. One fix along the way: changing the scroll element no longer carries over a pending iOS late-fling window, which could defer corrections on the new element for 150ms.#1318
4a1a4fd- fix(virtual-core): on iOS, defer scroll corrections only for touch-driven scrolls (a finger down, or the momentum after it), so a programmatic landing likescrollToOffsetcompensates before paint instead of snapping later#1319
3c61b6e- fix(virtual-core): hold a scroll correction the element cannot take instead of writing it (#1287)A prepend's anchor delta or an above-viewport size change that lands while a
scrollTopwrite is impossible (iOS during a touch gesture or its momentum tail, any WebKit while the element is rubber-banding past an edge) is now held:scrollOffsetcarries the corrected position, the rows and the total size are exposed shifted back by the held amount so every adapter keeps the reader's row where it is, and one write moves the element once a write is possible. Before, the write was discarded during the bounce on desktop Safari (the bounce stalled with the new rows and a blank top on screen), and on iOS the new rows showed through the bounce and snapped back at the flush.#1324
9c762fe- refactor(virtual-core): simplify the scroll-correction state (no behaviour change)movedflag.scrollAdjustmentsis deprecated: a correction is folded intoscrollOffsetat once, so it is always 0. ReadscrollOffsetalone; the getter stays.enabled: falseused to accumulate, and a correction made after re-enabling but before the next update was added on top of them. They are no longer carried over.@tanstack/vue-virtual@3.13.46
Patch Changes
56b2a63,d2c7911,9c762fe,6789f7a,77cb05e,4a1a4fd,3c61b6e,9c762fe]:@tanstack/virtual-benchmarks@0.0.23
Patch Changes