An in-range update of semver is breaking the build 🚨

[greenkeeper]

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

The dependency semver was updated from 7.1.3 to 7.2.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

semver is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

---

Commits

The new version differs by 2 commits.

• c6581a8 7.2.0
• 2b5ad50 Add method for simplifying ranges

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 7.1.3 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The dependency semver was updated from 7.2.0 to 7.2.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• dfe658f 7.2.1
• 6eab8c2 do not include vim swap files in package

See the full diff

[greenkeeper]

• The dependency semver was updated from 7.2.1 to 7.2.2.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

• 5d0dcda 7.2.2
• 044c54c fix: 2.0.0-rc1 should never be included in ^1.0.0
• 77c95e3 update changelog

See the full diff

[greenkeeper]

• The dependency semver was updated from 7.2.2 to 7.2.3.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

• 45b1495 7.2.3
• 0365d6f update tap to make npm audit happy
• 1bd5bdd fix: Handle prereleases properly in 'X - Y' ranges

See the full diff

[greenkeeper]

• The dependency semver was updated from 7.2.3 to 7.3.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

• 92bccf1 7.3.0
• 100f07a subset(): test if one range is a subset of another
• 33daffe changelog 7.2.3

See the full diff

[greenkeeper]

• The dependency semver was updated from 7.3.0 to 7.3.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

• b97044b 7.3.1
• 059a5ad Always exclude prereleases from range maximums
• f27dcf5 Adding several tests for various 'pre-release' situations.

See the full diff

[greenkeeper]

• The dependency semver was updated from 7.3.1 to 7.3.2.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• ce978f9 7.3.2
• 9fb2c19 Exclude prereleases in X-ranges with < comparators

See the full diff