Skip to content
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

fix(deps): update dependency vee-validate to v4 #5529

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 13, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vee-validate (source) 3.4.15 -> 4.13.2 age adoption passing confidence

Release Notes

logaretm/vee-validate (vee-validate)

v4.13.2

Compare Source

Patch Changes
  • afbd0e5: feat: support valibot 0.33.0

v4.13.1

Compare Source

v4.13.0

Compare Source

Minor Changes
Patch Changes
  • ae3772a: feat: expose setValue on Field instance and slot props closes #​4755
  • fd008c1: feat: added ResetFormOpts arg to useResetForm closes #​4707

v4.12.8

Compare Source

Patch Changes
  • f8bab9c: "fix: field-level validation not working with typed scheams closes #​4744"

v4.12.7

Compare Source

Patch Changes
  • 1376794: fix: handle meta.required for single field schemas closes #​4738
  • 1376794: fix: add try-catch for schema description logic across all major schema providers
  • c4415f8: fix: ensure meta.required is reactive whenever the schema changes closes #​4738

v4.12.6

Compare Source

Patch Changes
  • 07d01fd: fix: re-apply errors to avoid race conditions

v4.12.5

Compare Source

🐛 Bug Fixes

v4.12.4

Compare Source

Patch Changes
  • 2a09a58: "fix: check if both source and target objects are POJOs"

v4.12.3

Compare Source

Patch Changes
  • 72e4379: fix: remove deep data mutation warning closes #​4597
  • a18c19f: feat: allow path meta querying for nested fields closes #​4575
  • e2171f8: feat: expose some state on form instance

v4.12.2

Compare Source

Patch Changes
  • b2203c8: fix: apply schema casts when submitting closes #​4565
  • ec8a4d7: fix: defineField should respect global validateOnModelUpdate closes #​4567

v4.12.1

Compare Source

Patch Changes
  • 36f6b9e: fix: reset form and field behaviors for unspecified values closes #​4564
  • c1c6f39: fix: unref initial values when initializing the form closes #​4563

v4.12.0

Compare Source

Minor Changes
Patch Changes

v4.11.8

Compare Source

Patch Changes

v4.11.7

Compare Source

Patch Changes

v4.11.6

Compare Source

Patch Changes
  • f683e90: fix(types): infer the model value prop name correctly

v4.11.5

Compare Source

Patch Changes

v4.11.4

Compare Source

Patch Changes
  • 4d8ed7e: feat: added reset opts to force values closes #​4440
  • b53400e: fix: silent validation should not mark a field as validated
  • 8f680bf: fix: clone the schema object before validating closes #​4459
  • 5231f43: fix: respect validate on model update configuration closes #​4451, closes #​4467

v4.11.3

Compare Source

v4.11.2

Compare Source

Patch Changes
  • 2ff045c: fix: do not warn if a form or a field was resolved closes #​4399
  • 73219b4: feat: expose all internal types
  • 4947e88: feat: expose BaseInputBinds and BaseComponentBinds interfaces #​4409
  • ecbb690: feat: query fields meta state

v4.11.1

Compare Source

Patch Changes
  • 5e23dcb: fix: add support for parsing range inputs

v4.11.0

Compare Source

Minor Changes
  • 2d8143f: feat: added composition setter functions

v4.10.9

Compare Source

Patch Changes
  • c02337f: fix: correct the setErrors type to allow for string[]

v4.10.8

Compare Source

Patch Changes
  • a9a473b: feat(perf): improve performance setFieldError and setFieldValue closes #​4382

v4.10.7

Compare Source

Patch Changes
  • 9290f5a: fix: clone values inserted into field arrays closes #​4372
  • 93f8001: fix: do not warn if the validation is for removed paths closes #​4368

v4.10.6

Compare Source

Patch Changes

v4.10.5

Compare Source

Patch Changes
  • 6a1dc9b: fix: component blur event and respect model update config closes #​4346

v4.10.4

Compare Source

Patch Changes
  • 2f9ca91: fix(types): remove deep readonly type for now

v4.10.3

Compare Source

Patch Changes
  • 32537e1: fix: less strict object checks for undefined and missing keys closes #​4341
  • c3698f0: fix: respect model modifiers when emitting the value closes #​4333

v4.10.2

Compare Source

Patch Changes
  • 1660048: fix: define binds not respecting config events

v4.10.1

Compare Source

Patch Changes
  • fc41691: fix: handle NaN when parsing number inputs closes #​4328
  • 435e785: fix: reset present values after all path mutation
  • 273cca7: fix: reset field should not validate closes #​4323

v4.10.0

Compare Source

Minor Changes
  • 7a548f4: chore: require vue 3.3 and refactor types
  • 7ce9d67: feat(breaking): disable v-model support by default closes #​4283
  • bfd6b00: "feat: allow custom models for defineComponentBinds"
  • d4fafc9: "feat: allow handleBlur to run validations"
  • 05d957e: feat: mark form values as readonly closes #​4282
Patch Changes

v4.9.6

Compare Source

Patch Changes
  • b138282: fix(types): export SetFieldValueOptions interface closes #​4290
  • 6e074f7: fix: handleBlur should respect blur validate config closes #​4285

v4.9.5

Compare Source

Patch Changes

v4.9.4

Compare Source

Patch Changes
  • f4ea2c0: fix: exclude undefined and null from initial values closes #​4139

v4.9.3

Compare Source

Patch Changes
  • 09d5596: fix: run validation on value change closes #​4251
  • 9bfbfaa: feat: added isValidating to useForm
  • 48b45d9: fix: hoist nested errors path to the deepest direct parent closes #​4063

v4.9.2

Compare Source

Patch Changes
  • 31090e0: avoid double unset path with field array remove
  • 9046308: fixed validations running for unmounted fields
  • fe322a0: batch unsets and sort paths unset order for safer unsets closes #​4115

v4.9.1

Compare Source

Patch Changes
  • 681bbab: Added type-fest to core package dependencies

v4.9.0

Compare Source

Minor Changes
  • 41b5d39: Implemented path types into various form API functions
  • 9540908: Added component and input binds helpers
Patch Changes
  • 7554d4a: fix field array triggering validation when an item is removed
  • 298577b: setValues does not delete unspecified fields values

v4.8.6

Compare Source

Patch Changes
  • 6e0b055: Introduced official nuxt module package

v4.8.5

Compare Source

Patch Changes

All notable changes to this project will be documented in this file.
See Conventional Commits for commit guidelines.

v4.8.4

Compare Source

Bug Fixes
Features
  • allow name ref to be a lazy function (8fb543a)

v4.8.3

Compare Source

Note: Version bump only for package vee-validate

v4.8.2

Compare Source

Bug Fixes
  • do not use name as a default label for useField closes #​4164 (d5acff7)

v4.8.1

Compare Source

Bug Fixes
  • make sure to have a fallback for undefined casts closes #​4186 (9f1c63b)
Features
  • expose errorBag to slot props (371744e)

v4.8.0

Compare Source

Bug Fixes
  • finally handicap yup schema resolution (303b1fb)
  • initial sync with v-model if enabled closes #​4163 (1040643)
  • properly aggregrate nested errors for yup (7f90bbc)
  • remove console.log from devtools integration (3c2d51c)
  • remove yup schema type and rely on assertions (5cbb913)
  • render zod multiple errors in nested objects closes #​4078 (f74fb69)
  • run silent validation after array mutations closes #​4096 (044b4b4)
  • type inference fix (ac0383f)
  • watch and re-init array fields if form data changed closes #​4153 (6e784cc)
Features

4.7.4 (2023-02-07)

Bug Fixes
Features

4.7.3 (2022-11-13)

Bug Fixes

4.7.2 (2022-11-02)

Bug Fixes

4.7.1 (2022-10-23)

Bug Fixes

v4.7.4

Compare Source

Bug Fixes
Features

v4.7.3

Compare Source

Bug Fixes

v4.7.2

Compare Source

Bug Fixes

v4.7.1

Compare Source

Bug Fixes

v4.7.0

Compare Source

Features

4.6.10 (2022-09-30)

Bug Fixes
  • use ssr safe file check (56663aa)

4.6.9 (2022-09-19)

Bug Fixes

4.6.8 (2022-09-19)

Bug Fixes
Features

4.6.7 (2022-08-27)

Bug Fixes
  • allow generics for generic function type (91e97aa)
  • handle validation races for async validations (#​3908) (8c82079)

4.6.6 (2022-08-16)

Bug Fixes

4.6.5 (2022-08-11)

Bug Fixes

4.6.4 (2022-08-07)

Bug Fixes
  • make sure to deep watch created models by useFieldModel (fbe273c)

4.6.3 (2022-08-07)

Features
  • Expose InvalidSubmissionHandler and GenericValidateFunction types (#​3853) (3ccf27d)

4.6.2 (2022-07-17)

Bug Fixes
Features

4.6.1 (2022-07-12)

Bug Fixes

v4.6.10

Compare Source

Bug Fixes
  • use ssr safe file check (56663aa)

v4.6.9

Compare Source

Bug Fixes

v4.6.8

Compare Source

Bug Fixes
Features

v4.6.7

Compare Source

Bug Fixes
  • allow generics for generic function type (91e97aa)
  • handle validation races for async validations (#​3908) (8c82079)

v4.6.6

Compare Source

Bug Fixes

v4.6.5

Compare Source

Bug Fixes

v4.6.4

Compare Source

Bug Fixes
  • make sure to deep watch created models by useFieldModel (fbe273c)

v4.6.3

Compare Source

Features
  • Expose InvalidSubmissionHandler and GenericValidateFunction types (#​3853) (3ccf27d)

v4.6.2

Compare Source

Bug Fixes
Features

v4.6.1

Compare Source

Bug Fixes
  • use ssr safe file check (56663aa)

v4.6.0

Compare Source

Bug Fixes
  • added existing undefined path fallback closes #​3801 (fd0500c)
  • avoid inserting value binding for file type inputs closes #​3760 (3c76bb2)
  • avoid validating when field instance exists (3759df2)
  • compare form meta.dirty based on original values than staged initials closes #​3782 (f3ffd3c)
  • expose ValidationOptions type closes #​3825 (9854865)
  • exposed component APIs to their TS defs with refs closes #​3292 (ae59d0f)
  • fast equal before deciding value was changed closes #​3808 (3d582ec)
  • use multiple batch queues for both validation modes closes #​3783 (6156603)
Features

4.5.11 (2022-04-10)

Bug Fixes
Features

4.5.10 (2022-03-08)

Note: Version bump only for package vee-validate

4.5.9 (2022-02-22)

Bug Fixes
  • mark fields validated via form validate as validated (ad9fa9d)

4.5.8 (2022-01-23)

Bug Fixes
  • clear old error path error when changing field name closes #​3664 (f736e62)
  • field array swap not working when falsy values are present at paths (40afbd9)

4.5.7 (2021-12-07)

Bug Fixes

4.5.6 (2021-11-17)

Bug Fixes

4.5.5 (2021-11-01)

Bug Fixes

4.5.4 (2021-10-20)

Note: Version bump only for package vee-validate

4.5.3 (2021-10-17)

Features

4.5.2 (2021-09-30)

Bug Fixes

4.5.1 (2021-09-29)

Note: Version bump only for package vee-validate

v4.5.11

Compare Source

Bug Fixes
Features

v4.5.10

Compare Source

Note: Version bump only for package vee-validate

v4.5.9

Compare Source

Bug Fixes
  • mark fields validated via form validate as validated (ad9fa9d)

v4.5.8

Compare Source

Bug Fixes
  • clear old error path error when changing field name closes #​3664 (f736e62)
  • field array swap not working when falsy values are present at paths (40afbd9)

v4.5.7

Compare Source

Bug Fixes

v4.5.6

Compare Source

Bug Fixes

v4.5.5

Compare Source

Bug Fixes

v4.5.4

Compare Source

Note: Version bump only for package vee-validate

v4.5.3

[Compare Source](https://togithub.com/logaretm/ve


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

Copy link
Contributor Author

renovate bot commented Jul 13, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: frontend/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @ecamp3/frontend@undefined
npm error Found: [email protected]
npm error node_modules/vue
npm error   vue@"2.7.15" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vue@"^3.4.26" from [email protected]
npm error node_modules/vee-validate
npm error   vee-validate@"4.13.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-07-13T02_22_01_190Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-13T02_22_01_190Z-debug-0.log

@renovate renovate bot added the renovate label Jul 13, 2024
@BacLuc
Copy link
Contributor

BacLuc commented Jul 15, 2024

We need to update to vue3 for this

@BacLuc BacLuc closed this Jul 15, 2024
Copy link
Contributor Author

renovate bot commented Jul 15, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/vee-validate-4.x branch July 15, 2024 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant