Repository navigation
chore: version packages - #347
Merged
Merged
Conversation
blove
enabled auto-merge (squash)
August 13, 2026 01:18
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Vercel preview readyPreview: https://pretable-3zbp16cd3-cacheplane.vercel.app Updated automatically by the |
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
@pretable/react@0.5.2
Patch Changes
Stop re-estimating the height of a row that has already been measured. (#342)
When a streaming update replaced a row's data, the row layout controller published a fresh
estimateDomRowHeightvalue for it — even though the DOM had already reported that row's realheight. The estimate and the measurement disagree for any wrapped column, so every update swapped
one for the other and the rows below it jumped. On the homepage hero grid, which streams cell
updates into a wrapped column, this read as continuous jitter.
The controller now retains the last measured height per data-row identity and uses it as the
estimate gate's fallback, so an estimate is only ever used for a row that has never been measured.
Measured in Chrome against the hero grid, estimator-valued publications over a streaming run
dropped from 71 to 0.
Retention is bounded by a new
maxRetainedRowHeightsoption and is scoped to data rows; groupentries are never retained, since the estimate gate that consumes retained heights is itself gated
on data rows.
Updated dependencies []:
@pretable/core@0.5.2
@pretable/stream-adapter@0.5.2
@pretable/ui@0.5.2
@pretable/app-bench@0.0.25
Patch Changes
77febe7]:@pretable/app-website@0.0.25
Patch Changes
77febe7]: