Update proxyquire to the latest version 🚀 #148
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
googlebot
added
the
cla: yes
Codecov Report
@@ Coverage Diff @@
## master #148 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 12 12
Lines 1729 1729
=====================================
Hits 1729 1729Continue to review full report at Codecov.
|
alexander-fenster
approved these changes
Mar 7, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☝️ 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.
Release Notes
v2.0.0Fixes a bug where relative paths were not properly resolved and could conflict (#190). This may break your tests if they relied on buggy behavior.
Commits
The new version differs by 7 commits.
26baa502.0.0c375628Resolve relative paths relative to the module under test (#190)99dad5cremove unused variable from testd20312eadd tests asserting array behavior4bbad52travis: test on 3 latest lts releases (4/6/8)d09cbcause standard to lint project62de97creadme: make module paths relative (#168)See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴