- Notifications
You must be signed in to change notification settings - Fork4
Update supertest to the latest version 🚀#7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Version3.3.0 just got published.Update to this version instead 🚀 Release Notesv3.3.0#509 - Fix#486, bug in _assertBody, switch to CommitsThe new version differs by 10 commits.
See thefull diff |
Update to this version instead 🚀 Release Notes for v3.4.0
CommitsThe new version differs by 14 commits.
See thefull diff |
Update to this version instead 🚀 CommitsThe new version differs by 9 commits.
See thefull diff |
Update to this version instead 🚀 Release Notes for v4.0.0CommitsThe new version differs by 17 commits.
There are 17 commits in total. See thefull diff |
Update to this version instead 🚀 Release Notes for Fix - Superagent downgradedCommitsThe new version differs by 6 commits.
See thefull diff |
Update to this version instead 🚀 Release Notes for DocumentationCommitsThe new version differs by 5 commits.
See thefull diff |
Version3.2.0 ofsupertest was just published.
The version3.2.0 isnot covered by yourcurrent 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 supertest.
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
v3.2.0Commits
The new version differs by 29 commits.
c52338bMerge pull request #508 from visionmedia/prepare-releasefb3d042chore(package*.json) version bumped v3.2.08707c22doc(History.md) file updated05272d7Merge pull request #507 from visionmedia/upgrade-dependencies011d008chore(.gitignore) coverage folder included92578c7Merge pull request #503 from visionmedia/upgrade-dependencies1fc760bchore(package-lock.json) locker file updatedf8229a8Merge branch 'master' into upgrade-dependencies979999fMerge pull request #506 from rimiti/fix-pipeline96af26achore(.gitignore) .nyc_output folder includedb0a9dbdchore(.travis.yml) call npm coverage scriptc4566f2chore(package-lock.json) file updated85b17c6chore(package.json) coverage script created977081fMerge pull request #504 from visionmedia/adding-coverage0a3ad28Merge remote-tracking branch 'origin/master' into adding-coverageThere are 29 commits in total.
See thefull diff
FAQ and help
There is a collection offrequently asked questions. If those don’t help, you can alwaysask the humans behind Greenkeeper.
YourGreenkeeper bot 🌴