An in-range update of greenkeeper-lockfile is breaking the build 🚨
Closed this issue · 1 comments
greenkeeper commented
Version 1.7.2 of greenkeeper-lockfile just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | greenkeeper-lockfile |
| Current Version | 1.7.1 |
| Type | devDependency |
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
- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Release Notes
v1.7.2<a name"1.7.2">
1.7.2 (2017-07-11)
Bug Fixes
Commits
The new version differs by 1 commits.
d5c3129fix(yarn): don't use -S when installing regular dependencies (#45)
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 🌴
greenkeeper commented
After pinning to 1.7.1 your tests are passing again. Downgrade this dependency 📌.