-
Notifications
You must be signed in to change notification settings - Fork 4
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 our terms of service and privacy 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?
Conversation
Version 3.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 the full diff |
Update to this version instead 🚀 Release Notes for v3.4.0
CommitsThe new version differs by 14 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 9 commits.
See the full 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 the full diff |
Update to this version instead 🚀 Release Notes for Fix - Superagent downgradedCommitsThe new version differs by 6 commits.
See the full diff |
Update to this version instead 🚀 Release Notes for DocumentationCommitsThe new version differs by 5 commits.
See the full diff |
Version 3.2.0 of supertest was just published.
The version 3.2.0 is not covered by your current 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.
c52338b
Merge pull request #508 from visionmedia/prepare-release
fb3d042
chore(package*.json) version bumped v3.2.0
8707c22
doc(History.md) file updated
05272d7
Merge pull request #507 from visionmedia/upgrade-dependencies
011d008
chore(.gitignore) coverage folder included
92578c7
Merge pull request #503 from visionmedia/upgrade-dependencies
1fc760b
chore(package-lock.json) locker file updated
f8229a8
Merge branch 'master' into upgrade-dependencies
979999f
Merge pull request #506 from rimiti/fix-pipeline
96af26a
chore(.gitignore) .nyc_output folder included
b0a9dbd
chore(.travis.yml) call npm coverage script
c4566f2
chore(package-lock.json) file updated
85b17c6
chore(package.json) coverage script created
977081f
Merge pull request #504 from visionmedia/adding-coverage
0a3ad28
Merge remote-tracking branch 'origin/master' into adding-coverage
There are 29 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴