-
Notifications
You must be signed in to change notification settings - Fork 1
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 upath is breaking the build 🚨 #20
Comments
After pinning to 1.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 1.0.4 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 4 commits.
See the full diff |
Version 1.0.5 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 1.1.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 1.0.3 of upath was just published.
This version is covered by your current version range and after updating it in your project the build failed.
upath 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 2 commits.
f2a64fc
fix: sep returns '/' for seamless replacement fix #11
b40e2bc
chore: fix lodash dep for specs & test for node 8 & 9
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: