[Snyk] Upgrade envalid from 7.2.2 to 7.3.1

[mongoloidkhulmikuki366385]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to upgrade envalid from 7.2.2 to 7.3.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 5 versions ahead of your current version.
• The recommended version was released 7 months ago, on 2022-04-07.

Release notes

Package name: envalid

• 7.3.1 - 2022-04-07
  

  7.3.1

• 7.3.0 - 2022-03-02
  

  7.3.0

• 7.3.0-beta.3 - 2022-02-20
  

  7.3.0-beta.3

• 7.3.0-beta.2 - 2022-02-09
  

  7.3.0-beta.2

• 7.3.0-beta.1 - 2022-02-07
  

  7.3.0-beta.1

• 7.2.2 - 2021-10-27
  

  7.2.2

from envalid GitHub release notes

Commit messages

Package name: envalid

• ca9e176 7.3.1
• 96d55f3 Rename new envalidLogger to envalidErrorFormatter and update tests
• 3e60037 Expose an 'envalidLogger' function (#183)
• 83398bc Clarify that NODE_ENV needs to be set for devDefault to work (#186)
• 31d144e 7.3.0
• 73c29e9 Dependency updates, including to TS 4.6.2
• d64ed14 7.3.0-beta.3
• b2e7720 fix: environment variables being skipped after devDefault or default value is read (#182)
• b379334 7.3.0-beta.2
• 2038cbb Bump typescript to 4.6.0-beta, see https://github.com/Ensure default values don't go through validation, fix type narrowing from defaults af/envalid#176#issuecomment-1031924501
• 17664dd 7.3.0-beta.1
• 13e44d7 Dependency updates
• ef5a895 Ensure default values don't go through validation, fix type narrowing from defaults (#176)
• ed843a1 Add note about structuredClone to readme
• 086609b Small tweaks to new tests
• 94ea57a Remove node 10 from CI (husky doesn't support it), fix codeql specified branch
• 53af8de Update dependencies, fix error new in TS 4.4, add start command
• 8a088df Bump ansi-regex from 5.0.0 to 5.0.1 (#175)
• 6c4cdc7 Bump tmpl from 1.0.4 to 1.0.5 (#170)
• 418771a Fix issue #139, validator return type is too broad (#146)

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

[performance-testing-bot]

Unable to locate .performanceTestingBot config file

[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 detected.
• 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.