Skip to content

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

@greenkeeper

Description

@greenkeeper

Version 5.4.0 of semver just got published.

Branch Build failing 🚨
Dependency semver
Current Version 5.3.0
Type dependency

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 this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 16 commits.

  • e1c49c8 v5.4.0
  • 3ebc11d more test coverage
  • 5b30513 speed up tests a lot, add coverage
  • e1668ce add top level intersects function
  • 6cb2bcb intersection: use semver.version, not semver.raw
  • 4bacbfa Make exposed apis more clear
  • 8b86a26 Reduce line length and remove unused platform parameter
  • 99f133e Add range and comparator intersection docs to README
  • afbe8ca Move methods to comparator and range
  • 67c9ed7 Add support for range and comparators comparison
  • caeeac4 remove 0.x from Travis, cache npm stuff, use containers
  • bdda1a4 Add Node.js 8 to .travis.yml
  • 8fff305 Add node 6 to travis
  • aaba710 Added syntax highlighting to readme example
  • 32802c5 minimize heap allocations for maxSatisfying/minSatisfying

There are 16 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions