Update supertest 6.2.4 → 6.3.4 (minor) #96
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ supertest (6.2.4 → 6.3.4) · Repo · Changelog
Release Notes
6.3.4
6.3.3
6.3.2
6.3.1
6.3.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 42 commits:
6.3.4chore: bump deps, remove yarn.lockchore: bump depsMerge pull request #811 from ladjs/dependabot/npm_and_yarn/cookiejar-2.1.4Merge pull request #814 from siddtheone/patch-1Merge pull request #828 from 9renpoto/9renpoto-patch-1si/visionmedia/ladjs/Update package.jsonMerge pull request #821 from yunnysunny/feature/ci-fixci: fix broken github action cache savingMerge pull request #818 from lamweili/patch-1docs: fixed links (for #621)Update README.mdRemoving unused importchore(deps): bump cookiejar from 2.1.3 to 2.1.4Merge pull request #646 from dtom90/patch-1Merge pull request #621 from RichieRunner/patch-16.3.3chore: bump deps6.3.2docs: added maintainer notedocs: fixed links6.3.1fix: bump superagent (closes #798)6.3.0fix: lint package.json, added files arrayMerge pull request #793 from lamweili/feat/http2Merge pull request #795 from lamweili/code-coverageMerge pull request #794 from lamweili/migrate-covtest(#767): 100% code coverageci: migrated code coverage from coveralls to codecovfeat: supports http2Merge pull request #767 from alexandre-abrioux/expect-stacktraceMerge pull request #774 from jmccure/update-promise-example-readmeMerge pull request #792 from lamweili/refactor/testci: added cirefactor(test): do not hardcode any ports, use ephemeral portsrefactor(test): do not have both `s` and `server`, renamed to `server` for consistencytest: 100% test coveragerefactor(TestAgent): removed the host param when creating `Test` objectfeat(TestAgent): decoupled TestAgent and superagent's Agent to support more than `ca`, `key`, `cert`fix(TestAgent): attach cookies to agent after plugin is used👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.