The version 2.1.1 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of prepare-response.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 91.102% when pulling 34a58bef3cb85ac936a5ce4d02397b91167f699f on greenkeeper/prepare-response-2.1.1 into 47b0faf24518b78830d7de894484fc6e99ac46da on master.
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 2.1.1 of prepare-response was just published.
The version 2.1.1 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of prepare-response.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 11 commits.
a2afd69
Fix breakage with new mime
c6f449d
fix(package): update mime to version 2.0.3 (#8)
19251aa
chore(package): update testit to version 3.0.0 (#6)
662c0b7
Only test on the latest node.js version
c94ea5f
Release 2.1.0
feedf62
Test without using express
6a18689
Release 2.0.0
8cd3d67
fix(package): update promise to version 8.0.0 (#4)
3d15941
fix(package): update ms to version 1.0.0 (#3)
7f0ba1a
Update badges
3b8f979
Release 1.1.3
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: