-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency @conform-to/zod to v1.2.2 #119
Open
renovate
wants to merge
1
commit into
dev
Choose a base branch
from
renovate/conform-to-zod-1.x
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
May 13, 2024 03:36
2a31597
to
fc0947f
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
May 27, 2024 22:28
fc0947f
to
de221a1
Compare
renovate
bot
changed the title
Update dependency @conform-to/zod to v1.1.3
Update dependency @conform-to/zod to v1.1.4
May 27, 2024
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
2 times, most recently
from
June 3, 2024 03:21
cbfddef
to
20b6877
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
June 17, 2024 22:02
20b6877
to
8974733
Compare
renovate
bot
changed the title
Update dependency @conform-to/zod to v1.1.4
Update dependency @conform-to/zod to v1.1.5
Jun 17, 2024
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
June 24, 2024 00:10
8974733
to
4daaf5e
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
2 times, most recently
from
July 8, 2024 00:48
6d52ce6
to
324d76d
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
July 15, 2024 01:58
324d76d
to
0c3ea9d
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
2 times, most recently
from
August 5, 2024 00:24
72aa14b
to
d19d164
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
August 5, 2024 03:03
d19d164
to
b145652
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
August 19, 2024 00:25
b145652
to
d026991
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
August 26, 2024 02:18
d026991
to
67ccbd9
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
3 times, most recently
from
September 13, 2024 21:55
8deb35b
to
9266a43
Compare
renovate
bot
changed the title
Update dependency @conform-to/zod to v1.1.5
Update dependency @conform-to/zod to v1.2.0
Sep 13, 2024
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
September 14, 2024 16:12
9266a43
to
1a6d5db
Compare
renovate
bot
changed the title
Update dependency @conform-to/zod to v1.2.0
Update dependency @conform-to/zod to v1.2.1
Sep 14, 2024
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
September 20, 2024 02:16
1a6d5db
to
8d19a52
Compare
renovate
bot
changed the title
Update dependency @conform-to/zod to v1.2.1
Update dependency @conform-to/zod to v1.2.2
Sep 20, 2024
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
2 times, most recently
from
September 23, 2024 03:34
7677d87
to
c2b0170
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
2 times, most recently
from
October 7, 2024 03:45
ead3d91
to
df4d0c6
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
2 times, most recently
from
October 21, 2024 01:07
e2b810e
to
23c22ba
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
November 4, 2024 00:06
23c22ba
to
362f826
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
November 11, 2024 00:39
362f826
to
60c6421
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
November 18, 2024 01:04
60c6421
to
74c355c
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
3 times, most recently
from
December 2, 2024 03:09
dd35867
to
fb14efb
Compare
renovate
bot
force-pushed
the
renovate/conform-to-zod-1.x
branch
from
December 16, 2024 00:16
fb14efb
to
9760890
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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 contains the following updates:
1.1.0
->1.2.2
Release Notes
edmundhung/conform (@conform-to/zod)
v1.2.2
Compare Source
What's Changed
fix: revert auto field value update (#778)
Revert https://github.com/edmundhung/conform/pull/729 and https://github.com/edmundhung/conform/pull/766
The auto field value update feature introduced in v1.2.0 has caused several critical issues with significant user impact. While I appreciate what they accomplished, I’ve realized the current solution isn't robust enough to handle all potential use cases. To minimize the impact on everyone, I believe it's best to revert these changes for now.
Full Changelog: edmundhung/conform@v1.2.1...v1.2.2
v1.2.1
Compare Source
What's Changed
Full Changelog: edmundhung/conform@v1.2.0...v1.2.1
v1.2.0
Compare Source
Embrace the platform
This change is reverted in v1.2.2
One of the most critical changes in this release is the auto field value update implemented in #729. Conform now updates input value using the DOM api instead of relying on the
key
to re-mount the inputs with the new defaultValue. It means:key
(e.g.fields.title.key
) to the input elements unless you are rendering a list.key
to the input element. If you were seeing the messageWarning: A props object containing a "key" prop is being spread into JSX
, it should be resolved now.Pre-release
Thanks to pkg.pr.new, we are now releasing a preview version on every pull request (#742)
You will find a comment on the PR like this one from pkg.pr.new with each package name listed. If you expand the item, you will see a command to install the pre-release version. If you are not using pnpm, you can swap it with npm install, or just copy the package URL and replace the version in the package.json with it.
We are also shipping a pre-release version on every commit merged to
main
in the formathttps://pkg.pr.new/@​conform-to/package@commit
. For example, if you would like to install the pre-release version of@conform-to/dom
and@conform-to/zod
up todb63782
, you can run:Other Improvements
submission.payload
in #706. If you were using Remix with single fetch, the action results should no longer be in typenever
. Thanks @timvandam!.default()
to set a fallback value. However,.default()
does not work as expected withz.string().default('')
. This issue has now been resolved, but keep in mind that the default value is still subject to validation errors. For more predictable results, we recommend using.transform(value => value ?? defaultValue)
instead.FormValue
should never benull
. Thanks @aaronadamsCA!control.value
in #721. Thanks @reborn2135!parseWithYup.md
andFormProvider.md
in #708, #751. Thanks @uttk, @felixyeboah!New Contributors
Full Changelog: edmundhung/conform@v1.1.5...v1.2.0
v1.1.5
Compare Source
Improvements
unstable_useControl
not resetting the value of the registered input on form reset (#674)Full Changelog: edmundhung/conform@v1.1.4...v1.1.5
v1.1.4
Compare Source
Improvements
New Contributors
Full Changelog: edmundhung/conform@v1.1.3...v1.1.4
v1.1.3
Compare Source
What's Changed
type
prop returned from thegetInputProps
helper by @AMEH64 in https://github.com/edmundhung/conform/pull/579instanceof
for Zod schemas by @colinhacks in https://github.com/edmundhung/conform/pull/601New Contributors
Full Changelog: edmundhung/conform@v1.1.2...v1.1.3
v1.1.2
Compare Source
What's Changed
Full Changelog: edmundhung/conform@v1.1.1...v1.1.2
v1.1.1
Compare Source
What's Changed
Full Changelog: edmundhung/conform@v1.1.0...v1.1.1
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "* 0-3 * * 1" (UTC).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.