Uh oh!
There was an error while loading. Please reload this page.
ci: Version Packages - #1213
Merged
Merged
Conversation
ContributorAuthor
🚀 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 9c6c081
☁️ Nx Cloud last updated this comment at |
github-actionsBotforce-pushed
the
changeset-release/main
branch
from
June 30, 2026 14:50
1f99bec to
9c6c081CompareUh oh!
There was an error while loading. Please reload this page.
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 freeto 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@5.0.7
Patch Changes
767ead4,bc8643b]:@tanstack/lit-virtual@3.13.32
Patch Changes
767ead4,bc8643b]:@tanstack/react-virtual@3.14.5
Patch Changes
767ead4,bc8643b]:@tanstack/solid-virtual@3.13.31
Patch Changes
767ead4,bc8643b]:@tanstack/svelte-virtual@3.13.31
Patch Changes
767ead4,bc8643b]:@tanstack/virtual-core@3.17.3
Patch Changes
#1206
767ead4- Cut per-scroll-frame allocations on the defaultlanes === 1path. Range computation previously allocated an options object and two closures on every scroll event; it now does the same work allocation-free, reducing GC pressure during continuous scroll.#1212
bc8643b- Don't latch a scroll direction from the read-back of the virtualizer's own adjustment writeapplyScrollAdjustmentfolds the pending adjustment intoscrollOffseteagerly, so the browser's scroll event for that write arrives at exactly the held offset. The scroll-direction computation treated that equality as'backward', which made the defaultshouldAdjustScrollPositionOnItemSizeChangeskip above-viewport re-measure compensation for the rest of theisScrollingResetDelaywindow — so during multi-frame reflows (e.g. a side pane's width animation re-wrapping rows while scrolled up) most frames went uncompensated and the viewport drifted. An event at the held offset carries no direction information, so the direction now stays unchanged in that case; real gestures always move the offset and still latch normally.@tanstack/vue-virtual@3.13.31
Patch Changes
767ead4,bc8643b]:@tanstack/virtual-benchmarks@0.0.8
Patch Changes