An in-range update of semver is breaking the build π¨
greenkeeper opened this issue Β· 3 comments
Version 5.5.0 of semver was just published.
Branch | Build failing π¨ |
---|---|
Dependency | semver |
Current Version | 5.4.1 |
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, 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/travis-ci/push The Travis CI build could not complete due to an error Details
Commits
The new version differs by 7 commits.
44cbc84
v5.5.0
1d37529
Cleaned up coerce behavior
e7092b4
Improved coerce regex and added coerce to README.
68cef2d
Added version coercion to the module and CLI.
ec6f97a
range.bnf: Fix invalid bracket expression
906b664
travis: don't cache node_modules
7184ff4
range.bnf: Remove unnecessary empty entry
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 π΄
After pinning to 5.4.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Version 5.5.1 just got published.
Your tests are passing again with this version. Explicitly upgrade to this version π
- The
dependency
semver was updated from5.5.1
to5.6.0
.
Your tests are passing again with this update. Explicitly upgrade to this version π