Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jan 23, 2026

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/react-form@1.28.0

Minor Changes

  • add useTypedAppFormContext (#1826)

Patch Changes

  • fix: flatten errors consistently when validating before field mount (#2003)

    Fixed an issue where field.errors was incorrectly nested as [[error]] instead of [error] when form.validate() was called manually before a field was mounted. The flat(1) operation is now applied by default unless disableErrorFlat is explicitly set to true, ensuring consistent error structure regardless of when validation occurs.

  • Updated dependencies [41faffe, 7f2453b]:

    • @tanstack/form-core@1.28.0

@tanstack/angular-form@1.28.0

Patch Changes

  • fix: flatten errors consistently when validating before field mount (#2003)

    Fixed an issue where field.errors was incorrectly nested as [[error]] instead of [error] when form.validate() was called manually before a field was mounted. The flat(1) operation is now applied by default unless disableErrorFlat is explicitly set to true, ensuring consistent error structure regardless of when validation occurs.

  • Updated dependencies [41faffe, 7f2453b]:

    • @tanstack/form-core@1.28.0

@tanstack/form-core@1.28.0

Patch Changes

  • fix: flatten errors consistently when validating before field mount (#2003)

    Fixed an issue where field.errors was incorrectly nested as [[error]] instead of [error] when form.validate() was called manually before a field was mounted. The flat(1) operation is now applied by default unless disableErrorFlat is explicitly set to true, ensuring consistent error structure regardless of when validation occurs.

  • run validation for fields without instances (#2001)

@tanstack/form-devtools@0.2.13

Patch Changes

@tanstack/lit-form@1.23.20

Patch Changes

@tanstack/react-form-devtools@0.2.13

Patch Changes

  • Updated dependencies []:
    • @tanstack/form-devtools@0.2.13

@tanstack/react-form-nextjs@1.28.0

Patch Changes

  • Updated dependencies [41faffe, a7eda7a]:
    • @tanstack/react-form@1.28.0

@tanstack/react-form-remix@1.28.0

Patch Changes

  • Updated dependencies [41faffe, a7eda7a]:
    • @tanstack/react-form@1.28.0

@tanstack/react-form-start@1.28.0

Patch Changes

  • Updated dependencies [41faffe, a7eda7a]:
    • @tanstack/react-form@1.28.0

@tanstack/solid-form@1.28.0

Patch Changes

  • fix: flatten errors consistently when validating before field mount (#2003)

    Fixed an issue where field.errors was incorrectly nested as [[error]] instead of [error] when form.validate() was called manually before a field was mounted. The flat(1) operation is now applied by default unless disableErrorFlat is explicitly set to true, ensuring consistent error structure regardless of when validation occurs.

  • Updated dependencies [41faffe, 7f2453b]:

    • @tanstack/form-core@1.28.0

@tanstack/solid-form-devtools@0.2.13

Patch Changes

  • Updated dependencies []:
    • @tanstack/form-devtools@0.2.13

@tanstack/svelte-form@1.28.0

Patch Changes

@tanstack/vue-form@1.28.0

Patch Changes

  • fix: flatten errors consistently when validating before field mount (#2003)

    Fixed an issue where field.errors was incorrectly nested as [[error]] instead of [error] when form.validate() was called manually before a field was mounted. The flat(1) operation is now applied by default unless disableErrorFlat is explicitly set to true, ensuring consistent error structure regardless of when validation occurs.

  • Updated dependencies [41faffe, 7f2453b]:

    • @tanstack/form-core@1.28.0

@github-actions github-actions bot force-pushed the changeset-release/main branch from d00e8d2 to 65cf6de Compare January 24, 2026 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant