The version 1.8.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of greenkeeper-lockfile.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notesv1.8.0
<a name"1.8.0">
1.8.0 (2017-08-08)
Features
allow package-json.lock and yarn.lock to be uppdated simultaneously, (#42) (ae87c20b, closes #39, #39)
Commits
The new version differs by 3 commits.
ae87c20feat: allow package-json.lock and yarn.lock to be uppdated simultaneously, fixes #39 (#42)
8b34918Checks if branchName is falsy, instead of null/undefined
6e98c18Check that info.branchName exists before working with it
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 1.8.0 of greenkeeper-lockfile just got published.
The version 1.8.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of greenkeeper-lockfile. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v1.8.0<a name"1.8.0">
1.8.0 (2017-08-08)
Features
Commits
The new version differs by 3 commits.
ae87c20feat: allow package-json.lock and yarn.lock to be uppdated simultaneously, fixes #39 (#42)8b34918Checks if branchName is falsy, instead of null/undefined6e98c18Check that info.branchName exists before working with itSee the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: