chore: version packages - #560
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
blove
enabled auto-merge (squash)
September 1, 2026 02:44
Contributor
Vercel preview readyPreview: https://pretable-enbfksk6y-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.3
Patch Changes
useLocalRowModelnow treats an invalidrowsorderivationsupdate as a (#559)rejected write rather than a fatal one, matching
usePretable. A bad row (aduplicate id, a throwing accessor, a missing or non-scalar id, a null row)
previously threw out of a layout effect and unmounted whatever subtree renders
the model. The model now keeps the rows it already had and warns once, and a
later valid
rowsarray recovers.The caveats are the ones
usePretablecarries: the model can stay divergedfrom your data indefinitely, the warning latches per fault kind, and there is
no API to ask whether the rows it reports match the ones you passed. Treat the
warning as the signal. Its key is prefixed
local-so a rejection here cannever be silenced by — or mistaken for — one from
usePretable.This supersedes the closing note in 0.14.2, which recorded that
useLocalRowModelwas still fatal. That was accurate when it shipped; it is nolonger.
A lifecycle fault still propagates: writing to a disposed model, re-entering a
mutation, or any row-model code this guard has not been taught about reaches
you as a throw. So does an invalid
rowsoption at MOUNT, which is builtduring render and never reaches the guarded effect.
Updated dependencies []:
@pretable/core@0.14.3
@pretable/stream-adapter@0.14.3
@pretable/ui@0.14.3