chore: version packages - #554
Merged
Merged
Conversation
blove
enabled auto-merge (squash)
August 31, 2026 05:53
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
Vercel preview readyPreview: https://pretable-r7lzo4uvf-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.14.1
Patch Changes
An invalid
queryarriving on the prop after mount is a rejected write, not a (#553)destroyed grid.
The compiler's validation error was thrown synchronously out of the same layout
effect that already guards derivations, so it escaped the commit and React
unmounted the grid subtree — measured as rows 3 → 0 and a container of 0 bytes.
Two faults reach it, both from an ordinary
queryprop: a filter whose operatorrequires an operand and has none, and a
rowGroupsentry naming a column themodel does not have.
The update is now rejected whole: the row model keeps the query it already had,
the grid stays interactive and keeps painting the rows that query selected, and a
later valid query still lands. The rejection is reported through
warnOnce, keyedon the column, the fault location and the detail, so a second, different fault
still warns instead of being swallowed by the first one's latch.
Two throws are deliberate and unchanged. Mount still throws: there is no running
grid to protect, and a hard error surfaces a config bug at its cheapest moment.
An uncontrolled
grid.setQuerystill throws synchronously to its caller, whoasked for the write, can catch it, and whose grid survives either way.
Updated dependencies []:
@pretable/core@0.14.1
@pretable/stream-adapter@0.14.1
@pretable/ui@0.14.1