chore: version packages - #551
Merged
Merged
Conversation
blove
enabled auto-merge (squash)
August 31, 2026 03:48
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
Vercel preview readyPreview: https://pretable-hte5catj5-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
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
@pretable/react@0.13.1
Patch Changes
An invalid
aggregatearriving after mount is a rejected write, not a destroyed (#550)grid.
The compiler's validation error was thrown synchronously out of the derivations
layout effect, so it escaped the commit and React unmounted the grid subtree —
measured as group rows 1 → 0 and a container of 0 bytes. Both doors into the
derivations seam were fatal: a bad
aggregatewritten throughsetColumnAggregate, and — the one every consumer can reach, with no pane, nogrouping state and no knowledge of this feature — a bad
aggregateon thecolumnsprop on update.The update is now rejected whole: the row model keeps the derivations it already
had, the grid stays interactive and keeps painting the values it was showing, and
a later valid update still lands. The rejection is reported through
warnOnce,keyed on the column, the fault location and the detail, so a second, different
misconfiguration still warns instead of being swallowed by the first one's latch.
Mount still throws, deliberately: there is no running grid to protect and a hard
error surfaces a config bug at its cheapest moment.
Updated dependencies []:
@pretable/core@0.13.1
@pretable/stream-adapter@0.13.1
@pretable/ui@0.13.1