[Snyk] Upgrade express-validator from 6.15.0 to 7.0.1 #10412
Merged
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 express-validator from 6.15.0 to 7.0.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.
Warning: This is a major version upgrade, and may be a breaking change.
Release notes
Package name: express-validator
-
7.0.1 - 2023-04-16
- Fixed
-
7.0.0 - 2023-04-15
- Minimum supported Node.js version is now 14+
- Removed deprecated APIs - #993
- Import paths
- Sanitization-only middlewares (e.g.
- Deprecated TypeScript types (
- Validation errors changed shape
- Field validation errors
- (TypeScript only) The
- Added validation for no unknown fields - #558, #578, #612, #1148, #809, #927, #1204
- Added globstars (deep wildcard) support - #790, #1137, #1216
- Added support for multiple custom validators/sanitizers in
- Added request-level bail - #1100, #1214
- Added a
- Added
- Added new error types to
- Validating/sanitizing arrays no longer drops all but the first value - #791, #755, #704, #1002
- Added missing
- Don't silently fail when setting
- @ Yoowatney made their first contribution in #1219
-
6.15.0 - 2023-02-16
- chore(deps): bump ua-parser-js from 0.7.32 to 0.7.33 by @ dependabot in #1208
- chore(deps): bump eta from 1.12.3 to 2.0.0 by @ dependabot in #1211
- chore(deps): bump http-cache-semantics from 4.1.0 to 4.1.1 by @ dependabot in #1210
- feat: update to support validator 13.9.0 by @ fedeci in #1212
from express-validator GitHub release notescheckSchema()warning that known validators are unknown when its value isfalse- #1223🚀 🙌 First major version in almost 4 years! 🚀 🤯
Thanks everybody for having the patience. Hopefully this version brings many improvements to your developer experience!
Breaking changes 💥
express-validator/checkandexpress-validator/filtersanitize(),sanitizeBody(), etc)ValidationParamSchemaandValidationSchema)isObject()validator now assumesoptions.strict = trueby defaultparamproperty has been renamed topathoneOf()validation errors no longer have aparam: '_error'propertyValidationErrortype is now a discriminated union, it might be necessary to useswitchorifstatements to check that you're dealing with the type that you want to debug/formatoneOf()signature changed: fromoneOf(chains, message)tooneOf(chains, options: { message, errorType })oneOf()default error structure now groups errors by their... validation group!, instead of in a flat listCheckout the migration guide for examples on how to work around some of these:
https://express-validator.github.io/docs/migration-v6-to-v7
New features ✨
checkSchema()- #552, #1180ExpressValidatorclass which allows adding "persistent" custom validators, sanitizers, and options - #1077, #1079, #1209oneOf()support to.if()- #1170oneOf()- #956, #1022Bug fixes 🐛
ko-KRtoMobilePhoneLocale- #1218, #1219withMessageandnotin schemas - #664New Contributors
Full Changelog: v6.15.0...v7.0.0
What's Changed
Full Changelog: v6.14.3...v6.15.0
Commit messages
Package name: express-validator
Compare
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:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs