ci: Version Packages #1937
Merged
ci: Version Packages #1937
Conversation
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
github-actions bot force-pushed the changeset-release/main branch from 160b81c to a38e628 Compare 
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
@tanstack/angular-form@1.27.4
Patch Changes
c753d5e]:@tanstack/form-core@1.27.4
Patch Changes
fix: prevent unnecessary re-renders when there are no async validators (#1929)
Fields were re-rendering twice on each keystroke because
isValidatingwas being set totruethenfalseeven when there were no async validators to run. This fix checks if there are actual async validators before toggling theisValidatingstate.Fixes
Fields re-render twice on each keystroke, based on validation state #1130@tanstack/form-devtools@0.2.7
Patch Changes
c753d5e]:@tanstack/lit-form@1.23.16
Patch Changes
c753d5e]:@tanstack/react-form@1.27.4
Patch Changes
fix(react-form): prevent array field re-render when child property changes (#1930)
Array fields with
mode="array"were incorrectly re-rendering when a property on any array element was mutated. This was a regression introduced in v1.27.0 by the React Compiler compatibility changes.The fix ensures that
mode="array"fields only re-render when the array length changes (items added/removed), not when individual item properties are modified.Fixes Entire
arrayField rerenders when a property on any array element is mutated (regression in 1.27.0) #1925Updated dependencies [
c753d5e]:@tanstack/react-form-devtools@0.2.7
Patch Changes
@tanstack/react-form-nextjs@1.27.4
Patch Changes
35921c9]:@tanstack/react-form-remix@1.27.4
Patch Changes
35921c9]:@tanstack/react-form-start@1.27.4
Patch Changes
35921c9]:@tanstack/solid-form@1.27.4
Patch Changes
Using any Signal inside the Form.AppField render function no longer causes the entire component to re-run whenever that Signal changes. (#1934)
Updated dependencies [
c753d5e]:@tanstack/solid-form-devtools@0.2.7
Patch Changes
@tanstack/svelte-form@1.27.4
Patch Changes
c753d5e]:@tanstack/vue-form@1.27.4
Patch Changes
c753d5e]: