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 b4910d0ad413cefeb671ecf9f083cd7073a7cc0d on greenkeeper-nock-9.0.13 into 85374f87db9f4469de2605b6b15632b317cc12be on master.
Coverage remained the same at 84.388% when pulling b4910d0ad413cefeb671ecf9f083cd7073a7cc0d on greenkeeper-nock-9.0.13 into 85374f87db9f4469de2605b6b15632b317cc12be on master.
Hello lovely humans,
nock just published its new version 9.0.13.
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 156 commits .
f268187
9.0.13: Revert #863
e2396c3
Merge pull request #880 from node-nock/revert-v9.0.12-issue-863
aa3d18c
Revert "Merge branch 'fasterize-fix_match_body'"
91302df
9.0.12: Use key length in array/object comparison
8333e3a
Merge branch 'fasterize-fix_match_body'
2060ca8
Merge branch 'fix_match_body' of https://github.com/fasterize/nock into fasterize-fix_match_body
7156fd6
[#863] Fix matchBody for object and array comparison
30881e2
9.0.11: Fixes for #856 (pending mocks) and #425 (multipart forms)
cd657a7
Merge pull request #834 from delijati/master
3957f02
Merge pull request #857 from disrupticons/fixing-issue-856
1cd6863
fixing test description
d7bced0
9.0.10: Versioned tested and better .npmignore
06684f1
adding test for multipart match body
934f1c3
Merge pull request #858 from fabiosantoscode/patch-1
7c1cd79
Add some big folders to .npmignore
There are 156 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.