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 greenkeeper-lockfile is breaking the build 🚨 #94
Comments
After pinning to 1.6.0 your tests are passing again. Downgrade this dependency 📌. |
Version 1.7.1 just got published.Your tests are passing again with this version. Explicitly upgrade to this version 🚀 Release Notesv1.7.1<a name"1.7.1"> 1.7.1 (2017-06-21)Bug Fixes
|
Version 1.7.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 Release Notesv1.7.2<a name"1.7.2"> 1.7.2 (2017-07-11)Bug Fixes |
Version 1.13.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 28 commits.
There are 28 commits in total. See the full diff |
Version 1.13.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 6 commits.
See the full diff |
Version 1.13.2 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 1.13.3 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 1.14.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 |
Version 1.15.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 27 commits.
There are 27 commits in total. See the full diff |
Version 1.7.0 of greenkeeper-lockfile just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As greenkeeper-lockfile is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Status Details
Release Notes
v1.7.0<a name"1.7.0">
1.7.0 (2017-06-20)
Bug Fixes
Features
Commits
The new version differs by 3 commits.
f62f2f3
fix(circleci): use CIRCLE_PREVIOUS_BUILD_NUM to detect the first push
a720a27
feat: basic wercker support
6a80f73
fix: invoke strict mode in scripts (#38)
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 🌴
The text was updated successfully, but these errors were encountered: