The version 2.0.0 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 proxyquire.
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 97.849% when pulling 8c146505a8fc54ecabaf8ee28cb8c5bde3f3989b on greenkeeper/proxyquire-2.0.0 into f96560f7d686e82c826e51efd4f73a92679b677b on master.
Coverage remained the same at 97.849% when pulling 8c146505a8fc54ecabaf8ee28cb8c5bde3f3989b on greenkeeper/proxyquire-2.0.0 into f96560f7d686e82c826e51efd4f73a92679b677b on master.
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 2.0.0 of proxyquire was just published.
The version 2.0.0 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 proxyquire.
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 7 commits.
26baa50
2.0.0
c375628
Resolve relative paths relative to the module under test (#190)
99dad5c
remove unused variable from test
d20312e
add tests asserting array behavior
4bbad52
travis: test on 3 latest lts releases (4/6/8)
d09cbca
use standard to lint project
62de97c
readme: make module paths relative (#168)
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: