release: bump packages version - #1282
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 1, 2026 11:30
0e8cc9a to
754244d
Compare
More templates
@conform-to/dom
@conform-to/react
@conform-to/valibot
@conform-to/validitystate
@conform-to/yup
@conform-to/zod
commit: |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
August 2, 2026 09:17
7eb1ccf to
6f49815
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 3, 2026 23:06
6f49815 to
d9f3975
Compare
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
@conform-to/dom@1.21.0
Minor Changes
3b64110: chore: remove deprecated Future APIs from the
/futureexportsstripEmptyValuesoption fromparseSubmission(), deprecated in v1.18.0, is now removed.valueoption fromreport(), deprecated in v1.20.0, is now removed. UsetargetValueinstead.invalidproperty from field and form metadata, deprecated in v1.9.1, is now removed. Use!validinstead.getZodConstraint()andgetValibotConstraint()exports, deprecated in v1.16.0, are now removed. UsegetConstraints()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 sameintentName. Plain intent values are preserved as submit intent payloads:Registered form intents continue to resolve through their handlers, while invalid form intents resolve to
undefined.3b64110: chore: remove deprecated Future APIs from the
/futureexportsstripEmptyValuesoption fromparseSubmission(), deprecated in v1.18.0, is now removed.valueoption fromreport(), deprecated in v1.20.0, is now removed. UsetargetValueinstead.invalidproperty from field and form metadata, deprecated in v1.9.1, is now removed. Use!validinstead.getZodConstraint()andgetValibotConstraint()exports, deprecated in v1.16.0, are now removed. UsegetConstraints()instead.92c5084: feat: accept URLSearchParams as the form default value
useFormcan now parse URL search parameters directly. The parameters are parsed only when the form is initialized or reset:3a5f872: Fix
DefaultValueto preserve string literal types soz.literal(...)schemas infer their literal value instead of widening tostring.ef1cb22: feat: add intent serialization to intent dispatchers
Intent dispatcher methods now expose a
serialize()method with the same arguments. Use the returned value withform.intentNameon a native submit button to trigger form intents for progressive enhancement.eb51fde: Deprecated the
valueoption on theupdate()function provided to the futureonSubmithandler. UsetargetValueinstead:onSubmit(event, { value, update }) { event.preventDefault(); update({ reset: true, - value, + targetValue: value, }); }valueremains available as an alias and will be removed in the next minor version. If both options are provided,targetValuetakes precedence.Patch Changes
@conform-to/valibot@1.21.0
Minor Changes
3b64110: chore: remove deprecated Future APIs from the
/futureexportsstripEmptyValuesoption fromparseSubmission(), deprecated in v1.18.0, is now removed.valueoption fromreport(), deprecated in v1.20.0, is now removed. UsetargetValueinstead.invalidproperty from field and form metadata, deprecated in v1.9.1, is now removed. Use!validinstead.getZodConstraint()andgetValibotConstraint()exports, deprecated in v1.16.0, are now removed. UsegetConstraints()instead.0500457: Deprecated the
includeValueoption on the futureformatResult()API.The option will be removed in the next minor release.
formatResult()will then always return botherrorandvalue, equivalent to the currentincludeValue: truebehavior.Patch Changes
@conform-to/zod@1.21.0
Minor Changes
3b64110: chore: remove deprecated Future APIs from the
/futureexportsstripEmptyValuesoption fromparseSubmission(), deprecated in v1.18.0, is now removed.valueoption fromreport(), deprecated in v1.20.0, is now removed. UsetargetValueinstead.invalidproperty from field and form metadata, deprecated in v1.9.1, is now removed. Use!validinstead.getZodConstraint()andgetValibotConstraint()exports, deprecated in v1.16.0, are now removed. UsegetConstraints()instead.0500457: Deprecated the
includeValueoption on the futureformatResult()API.The option will be removed in the next minor release.
formatResult()will then always return botherrorandvalue, equivalent to the currentincludeValue: truebehavior.Patch Changes
@conform-to/yup@1.21.0
Patch Changes