Update request-promise to version 4.1.0 🚀 #2426
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
ghost
added
the
Current coverage is 91.84% (diff: 100%)@@ master #2426 diff @@
==========================================
Files 95 95
Lines 10708 10708
Methods 1309 1309
Messages 0 0
Branches 1741 1741
==========================================
Hits 9835 9835
Misses 873 873
Partials 0 0
|
drew-gross
force-pushed
the
greenkeeper-request-promise-4.1.0
branch
from
541f9c7 to
815e4f2
Compare
|
@greenkeeperio-bot updated the pull request. |
1 similar comment
|
@greenkeeperio-bot updated the pull request. |
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.
Hello lovely humans,
request-promise just published its new version 4.1.0.
This version 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 request-promise.
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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 9 commits .
c63e3a3Version 4.1.054d27f6test: in addition to cancellation support94c2e30chore: updated promise-core445cdf6Merge pull request #123 from not-an-aardvark/113-cancellation-support6b9fd01Add cancellation support (fixes #113)27945f3docs: note for npm proxy users143666cVersion 4.0.2d36f511fix: use with module bundlersaf95f10chore: updated lint settingsSee the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade