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 nock.
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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 84.388% when pulling 22e946af0078d8528e618390cb9e37cbbbd06e3a on greenkeeper-nock-9.0.8 into 85374f87db9f4469de2605b6b15632b317cc12be on master.
Coverage remained the same at 84.388% when pulling 22e946af0078d8528e618390cb9e37cbbbd06e3a on greenkeeper-nock-9.0.8 into 85374f87db9f4469de2605b6b15632b317cc12be on master.
Hello lovely humans,
nock just published its new version 9.0.8.
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 nock. 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 :sparkles:
You rock!
:palm_tree:
The new version differs by 125 commits .
f8fb1e7
9.0.8: Fix for #754
b48913d
Merge pull request #836 from node-nock/greenkeeper-superagent-3.5.0
3f26630
Merge pull request #802 from aleung/fix-754
a92a3fb
Changelog
588aef9
9.0.7: Fix for #610
a783410
Merge pull request #829 from yodeyer/fixQs
a6cf549
chore(package): update superagent to version 3.5.0
343dc5d
Test against request 2.79.0, with which timeout issue occured.
9bf2621
Add Visual Studio Code folder into gitignore
6e8f337
Update the failed test case
cf4ee98
Fix https://github.com/node-nock/nock/issues/754
5856cde
9.0.6: Fix for #827
7197769
Merge pull request #828 from node-nock/bug-827-matchStringOrRegexp
f2ae8c1
Bug #827 Defensive coding around target
b9d2823
Fail if interceptor has query parameters but not the query
There are 125 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.