[Snyk] Upgrade semver from 6.3.0 to 7.3.5

[snyk-bot]

Snyk has created this PR to upgrade semver from 6.3.0 to 7.3.5.

ℹ️ 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.

• The recommended version is 15 versions ahead of your current version.
• The recommended version was released 10 months ago, on 2021-03-23.

Release notes

Package name: semver

• 7.3.5 - 2021-03-23
  

  7.3.5

• 7.3.4 - 2020-12-01
  

  7.3.4

• 7.3.3 - 2020-12-01
  

  7.3.3

• 7.3.2 - 2020-04-14
  

  7.3.2

• 7.3.1 - 2020-04-14
  

  7.3.1

• 7.3.0 - 2020-04-14
  

  7.3.0

• 7.2.3 - 2020-04-13
  

  7.2.3

• 7.2.2 - 2020-04-10
  

  7.2.2

• 7.2.1 - 2020-04-06
  

  7.2.1

• 7.2.0 - 2020-04-06
  

  7.2.0

• 7.1.3 - 2020-02-11
• 7.1.2 - 2020-01-31
• 7.1.1 - 2019-12-17
• 7.1.0 - 2019-12-17
• 7.0.0 - 2019-12-14
• 6.3.0 - 2019-07-23

from semver GitHub release notes

Commit messages

Package name: semver

• e79ac3a 7.3.5
• 0ce87d6 Correctly handle prereleases/ANY ranges in subset
• 15ed208 fix(subset): check any as superset
• 093b40f 7.3.4
• 93ff028 use modern lru-cache, not legacy
• 984a8d5 7.3.3
• 703ec39 Add lru-cache dep
• 2d01126 MinVersion failing for '^2.16.2 ^2.16' alike range
• a7acc5d spelling: satisfies
• e6f7919 spelling: intersection
• e08d916 Memoize range parsing
• 6088070 add a test for the coverage map
• bcab95a Reduce unnecessary Comparators in Range set
• 226e6dc Fixed variable names and comments
• ce978f9 7.3.2
• 9fb2c19 Exclude prereleases in X-ranges with < comparators
• b97044b 7.3.1
• 059a5ad Always exclude prereleases from range maximums
• f27dcf5 Adding several tests for various 'pre-release' situations.
• 92bccf1 7.3.0
• 100f07a subset(): test if one range is a subset of another
• 33daffe changelog 7.2.3
• 45b1495 7.2.3
• 0365d6f update tap to make npm audit happy

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