-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An in-range update of semver is breaking the build 🚨 #1092
Comments
After pinning to 6.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 9 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 12 commits.
See the full diff |
The dependency semver was updated from
6.0.0
to6.1.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
Commits
The new version differs by 7 commits.
0aea9ca
6.1.0
7b072bd
Range intersect supports wildcards and ~
78ea02a
tap@14
62b21ed
Remove --save option as it isn't required anymore
93c2f2d
Clarify some ^0.0.x & ~.0.0.x cases
e09ecf8
Clarify Caret Ranges
a3bcc39
Add semver.compareBuild function.
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 🌴
The text was updated successfully, but these errors were encountered: