[Snyk] Upgrade jquery-validation from 1.19.0 to 1.19.3

[snyk-bot]

Snyk has created this PR to upgrade jquery-validation from 1.19.0 to 1.19.3.

ℹ️ 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 3 versions ahead of your current version.
• The recommended version was released 6 months ago, on 2021-01-09.

The recommended version fixes:

Severity	Issue	PriorityScore (*)	Exploit Maturity
	Regular Expression Denial of Service (ReDoS) SNYK-JS-JQUERYVALIDATION-1056868	589/1000 Why? Has a fix available, CVSS 7.5	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: jquery-validation

• 1.19.3 - 2021-01-09
  

  1.19.3 / 2021-01-09

  Core

  • CVE-2021-21252: fixed Regular Expression Denial of Service vulnerability (#2371)
  • Replaced deprecated jQuery functions (#2335)

  Chore

  • Add Accessibility section to Readme (#2149)

  Localization

  • Add "pattern" translation for French (#2363)
  • add phone validate translate for Turkish translation (#2343)
• 1.19.2 - 2020-05-23
  

  1.19.2 / 2020-05-23

  Core

  • Core: Fixes deprecated calls to jQuery trim for compat with newer jQuery core versions (#2328)

  Contributors

  • Brighton Balfrey
  • Markus Staab
  • Brahim Arkni
• 1.19.1 - 2019-06-15
  

  1.19.1 / 2019-06-15

  Core

  • Change focus() to trigger("focus") (#2243)

  Build

  • Set jQuery as a peer dependency (#2248)

  Localization

  • Add zh_TW translation for step message (#2245)
  • Adding Serbian translation for step method message (#2251)

  Contributors

  • Ahmed Gaber
  • Brahim Arkni
  • Dusan Orlovic
  • Markus Staab
  • Ryan Chang
  • Stephen Scott
• 1.19.0 - 2018-11-28
  

  IMPORTANT NOTE

  Subresource Integrity hashes

  As of 1.18.0, we started to provide Subresource Integrity hashes of all distribution files.

  The hashes for the 1.19.0 release can be found in the file jquery-validation-sri.json under dist folder.

  ---

  Changelog:

  Additional

  • Don't fail when field is optional in CNPJBR & CPFBR rules (#2236)
  • Add validation rule for mobile number of Russia Federation (#2207)
  • Add Brazillian CNPJ validation rule (#2222)
  • Add Brazillian CNH number (Carteira Nacional de Habilitacao) (#2234)
  • Add ABA Routing Number Validation (#2216)

  Core

  • Fix contenteditable detection's regression introduced in #2142 (#2235)

  Localization

  • Add Swedish translation for pattern (#2227)

  Thanks to all the Contributors

  • Brahim Arkni
  • Cory Silva
  • jehadja
  • João Issamu Francisco
  • Julio Spader
  • Markus Staab
  • Saeed Prez
  • Zhiliang Xu

from jquery-validation GitHub release notes

Commit messages

Package name: jquery-validation

• 45b9e28 Release:1.19.3
• 5d8f29e Core: fixed Regular Expression Denial of Service vulnerability (#2371)
• b8d6646 Localization: Add "pattern" translation for French (#2363)
• b9c793c docs: Fix simple typo, atteched -> attached (#2345)
• 8319330 Update messages_tr.js (#2343)
• b0e3b11 Add Accessibility section to Readme (#2149)
• 79bed39 Core: Replaced deprecated jQuery functions
• af445b3 chore: added more release tasks
• cd1ce52 Build: Updating the master version to 1.19.3-pre.
• d3748a2 Core: Fixes deprecated calls to jQuery trim (#2328)
• 25a0f14 Create FUNDING.yml
• 5426dcb chore: updated build docs (#2288)
• 05e35ea Build: Updating the master version to 1.19.2-pre.
• 01ca879 Build: Set jQuery as a peer dependency (#2248)
• 824c989 Localization: Adding Serbian translation for step method message (#2251)
• a9c20ec Core: change focus() to trigger("focus") (#2243)
• d1c73fe Localization: Add zh_TW translation for step message (#2245)
• d9840a5 Build: Updating the master version to 1.19.1-pre.

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

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.