Skip to content

release: bump packages version - #1282

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

release: bump packages version#1282
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

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

@conform-to/dom@1.21.0

Minor Changes

  • 3b64110: chore: remove deprecated Future APIs from the /future exports

    • The stripEmptyValues option from parseSubmission(), deprecated in v1.18.0, is now removed.
    • The value option from report(), deprecated in v1.20.0, is now removed. Use targetValue instead.
    • The invalid property from field and form metadata, deprecated in v1.9.1, is now removed. Use !valid instead.
    • The getZodConstraint() and getValibotConstraint() exports, deprecated in v1.16.0, are now removed. Use getConstraints() instead.

@conform-to/react@1.21.0

Minor Changes

  • 2529931: feat: allow submit and form intents to share a field name

    resolveSubmission() now lets submit intents and form intents share the same intentName. Plain intent values are preserved as submit intent payloads:

    // submission.intent === 'delete'
    resolveSubmission(submission).intent;
    // { type: 'submit', payload: 'delete' }

    Registered form intents continue to resolve through their handlers, while invalid form intents resolve to undefined.

  • 3b64110: chore: remove deprecated Future APIs from the /future exports

    • The stripEmptyValues option from parseSubmission(), deprecated in v1.18.0, is now removed.
    • The value option from report(), deprecated in v1.20.0, is now removed. Use targetValue instead.
    • The invalid property from field and form metadata, deprecated in v1.9.1, is now removed. Use !valid instead.
    • The getZodConstraint() and getValibotConstraint() exports, deprecated in v1.16.0, are now removed. Use getConstraints() instead.
  • 92c5084: feat: accept URLSearchParams as the form default value

    useForm can now parse URL search parameters directly. The parameters are parsed only when the form is initialized or reset:

    const { form, fields } = useForm({
      defaultValue: new URLSearchParams(window.location.search),
    });
  • 3a5f872: Fix DefaultValue to preserve string literal types so z.literal(...) schemas infer their literal value instead of widening to string.

  • ef1cb22: feat: add intent serialization to intent dispatchers

    Intent dispatcher methods now expose a serialize() method with the same arguments. Use the returned value with form.intentName on a native submit button to trigger form intents for progressive enhancement.

  • eb51fde: Deprecated the value option on the update() function provided to the future onSubmit handler. Use targetValue instead:

     onSubmit(event, { value, update }) {
       event.preventDefault();
       update({
         reset: true,
    -    value,
    +    targetValue: value,
       });
     }

    value remains available as an alias and will be removed in the next minor version. If both options are provided, targetValue takes precedence.

Patch Changes

  • Updated dependencies [3b64110]
    • @conform-to/dom@1.21.0

@conform-to/valibot@1.21.0

Minor Changes

  • 3b64110: chore: remove deprecated Future APIs from the /future exports

    • The stripEmptyValues option from parseSubmission(), deprecated in v1.18.0, is now removed.
    • The value option from report(), deprecated in v1.20.0, is now removed. Use targetValue instead.
    • The invalid property from field and form metadata, deprecated in v1.9.1, is now removed. Use !valid instead.
    • The getZodConstraint() and getValibotConstraint() exports, deprecated in v1.16.0, are now removed. Use getConstraints() instead.
  • 0500457: Deprecated the includeValue option on the future formatResult() API.

    The option will be removed in the next minor release. formatResult() will then always return both error and value, equivalent to the current includeValue: true behavior.

Patch Changes

  • Updated dependencies [3b64110]
    • @conform-to/dom@1.21.0

@conform-to/zod@1.21.0

Minor Changes

  • 3b64110: chore: remove deprecated Future APIs from the /future exports

    • The stripEmptyValues option from parseSubmission(), deprecated in v1.18.0, is now removed.
    • The value option from report(), deprecated in v1.20.0, is now removed. Use targetValue instead.
    • The invalid property from field and form metadata, deprecated in v1.9.1, is now removed. Use !valid instead.
    • The getZodConstraint() and getValibotConstraint() exports, deprecated in v1.16.0, are now removed. Use getConstraints() instead.
  • 0500457: Deprecated the includeValue option on the future formatResult() API.

    The option will be removed in the next minor release. formatResult() will then always return both error and value, equivalent to the current includeValue: true behavior.

Patch Changes

  • Updated dependencies [3b64110]
    • @conform-to/dom@1.21.0

@conform-to/yup@1.21.0

Patch Changes

  • Updated dependencies [3b64110]
    • @conform-to/dom@1.21.0

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 0e8cc9a to 754244d Compare August 1, 2026 11:30
@pkg-pr-new

pkg-pr-new Bot commented Aug 1, 2026

Copy link
Copy Markdown
More templates

@conform-to/dom

npm i https://pkg.pr.new/@conform-to/dom@1282

@conform-to/react

npm i https://pkg.pr.new/@conform-to/react@1282

@conform-to/valibot

npm i https://pkg.pr.new/@conform-to/valibot@1282

@conform-to/validitystate

npm i https://pkg.pr.new/@conform-to/validitystate@1282

@conform-to/yup

npm i https://pkg.pr.new/@conform-to/yup@1282

@conform-to/zod

npm i https://pkg.pr.new/@conform-to/zod@1282

commit: 754244d

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 4 times, most recently from 7eb1ccf to 6f49815 Compare August 2, 2026 09:17
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 6f49815 to d9f3975 Compare August 3, 2026 23:06
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.

0 participants