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 supertest.
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.
PR-373 - Allow TestAgent pass a cert and key to request (thanks @toefraz)
PR-392 - Update Readme with promise example (thanks @ajouve)
PR-400 - Update to superagent 3 (thanks @alphashuro)
The new version differs by 24 commits .
199506dPrepare 3.0.0 release. Small readme updates, update dev libs.
1d82e5bAllow TestAgent pass a cert and key to request (#373)
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.
Hello lovely humans,
supertest just published its new version 3.0.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 supertest. 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:
GitHub Release
PR-373 - Allow TestAgent pass a cert and key to request (thanks @toefraz)
PR-392 - Update Readme with promise example (thanks @ajouve)
PR-400 - Update to superagent 3 (thanks @alphashuro)
The new version differs by 24 commits .
199506dPrepare 3.0.0 release. Small readme updates, update dev libs.1d82e5bAllow TestAgent pass a cert and key to request (#373)188f8f2Update readme (#392)bd63752Use superagent 3 (#400)3c16aa1Couple small updates to README5930d2cChange package.json to 2.0.1 version and update engines field.4d21f0dRemove node 0.12 from travis testing. A little early for 0.12 EOF but I want the new eslint libs which don't support 0.12.6fcd9b3Update dev deps. Fix couple lint issues. Add node v6 and remove 0.10 for travis tests.2026549Prepare for 2.0.1 release.e07e981fix request with content-length > 0 and content-encoding: gzip (#371)cf9f991Update Release History for v2.0.0df45dd7Handle server not-running & superagent system errors (#348)054ad57Prepare for 2.0.0 release.7ca0574Upgrade superagent to 2.x (#347)7d35f22Change 'super-agent' to 'superagent' in Readme. (#343)There are 24 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.