[Snyk] Upgrade vee-validate from 4.12.4 to 4.13.1 #2
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
Snyk has created this PR to upgrade vee-validate from 4.12.4 to 4.13.1. See this package in npm: vee-validate See this project in Snyk: https://app.snyk.io/org/elenore23/project/cd5f9ee5-8c00-4f6f-9b2c-cff011538c62?utm_source=github&utm_medium=referral&page=upgrade-pr
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 automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade vee-validate from 4.12.4 to 4.13.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 6 versions ahead of your current version.
The recommended version was released on a month ago.
Release notes
Package name: vee-validate
-
4.13.1 - 2024-06-06
-
4.13.0 - 2024-06-03
- Inject form values to
- Expose
- Added
- Apply Yup/Zod transformations on field-level rules #4713 (#4754) thanks to @ mehcode
- Allow custom interpolation options for i18n #4726 (#4727) thanks to @ zleight1
- The
- Offer an
-
4.12.8 - 2024-05-09
-
4.12.7 - 2024-05-06
- Handle
- Handle
- Ensure
- added missing integer translation (#4674) thanks to @ Bandeirex
-
4.12.6 - 2024-03-08
- Apply error messages again to prevent hoisted paths from being overridden 07d01fd
- Expose
- Updated valibot dependency #4658
-
4.12.5 - 2024-01-29
- Make sure removePathState removes the correct path state #4643 (#4649) thanks to @ bgoscinski
- Remove event arg from define field handlers for component compat #4637 (#4647)
-
4.12.4 - 2023-12-27
- Check if both source and target objects are POJOs before attempting to merge them (2a09a58)
from vee-validate GitHub release notes🆕
Updated
@ vee-validate/valibotto support valibot v0.31.0 #4756 (#4770) thanks to @ fabian-hiller🆕 Features
yupschema contexts when using field-level rules #4753 (27fe5c8)setValueon Field instance and slot props #4755 (ae3772a)ResetFormOptsarg touseResetForm#4707 (fd008c1)🐛 Bug Fixes
forceoption not behaving correctly when passing empty objects or empty values, now it respects whatever you pass in as the new values and initial values #4680 #4729 (454bc45)allexport that contains all rules for@ vee-validate/rules#4766 (fdb2d47)chore(release): publish
🐛 Bug Fixes
TypedSchema.describeAPI crashing with future releases, now it just reportsfalseformeta.required(1376794)meta.requiredfor single field schema react to changes #4738 (1376794)meta.requiredreacts to reactive form schema changes #4738 (c4415f8)🌍 i18n
🐛 Bug Fixes
👕 TypeScript
Fieldcomponent interface #4657🐛 Bug Fixes
🐛 Bug Fixes
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: