Skip to content
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

chore(deps): update dependency supertest to v6.3.3 #11749

Merged
merged 1 commit into from Jun 13, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 13, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
supertest 6.2.4 -> 6.3.3 age adoption passing confidence

Release Notes

visionmedia/supertest

v6.3.3

Compare Source

v6.3.2

Compare Source

v6.3.1

Compare Source

v6.3.0

Compare Source

  • fix: lint package.json, added files array 20adbc1
  • Merge pull request #​793 from lamweili/feat/http2 22b89b6
  • Merge pull request #​795 from lamweili/code-coverage a225e95
  • Merge pull request #​794 from lamweili/migrate-cov fa129dc
  • test(#​767): 100% code coverage 9c5bd92
  • ci: migrated code coverage from coveralls to codecov 46e6feb
  • feat: supports http2 da57804
  • Merge pull request #​767 from alexandre-abrioux/expect-stacktrace e064b5a
  • Merge pull request #​774 from jmccure/update-promise-example-readme ba4b43b
  • Merge pull request #​792 from lamweili/refactor/test b8c2e29
  • ci: added ci da1e842
  • refactor(test): do not hardcode any ports, use ephemeral ports 8847310
  • refactor(test): do not have both s and server, renamed to server for consistency c1c4402
  • test: 100% test coverage 8bf4c14
  • refactor(TestAgent): removed the host param when creating Test object 1c8930d
  • feat(TestAgent): decoupled TestAgent and superagent's Agent to support more than ca, key, cert 5e23869
  • fix(TestAgent): attach cookies to agent after plugin is used 6d9b9cb
  • Update promise example to work with Mocha 5862fe6
  • fix: add stacktrace to failed expect function call 3dba4e9
  • test: add failing test b24da85

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jun 13, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Jun 13, 2023

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: sample/33-graphql-mercurius/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: nest-typescript-starter@1.0.0
npm ERR! Found: mercurius@12.2.0
npm ERR! node_modules/mercurius
npm ERR!   mercurius@"12.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer mercurius@"^8.12.0 || ^9.0.0 || ^10.0.0" from @nestjs/mercurius@10.2.1
npm ERR! node_modules/@nestjs/mercurius
npm ERR!   @nestjs/mercurius@"10.2.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/ff8743/cafb3d/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/ff8743/cafb3d/cache/others/npm/_logs/2023-06-13T06_57_11_356Z-debug-0.log

File name: sample/13-mongo-typeorm/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: typeorm@0.3.16
npm ERR! Found: mongodb@3.6.0
npm ERR! node_modules/mongodb
npm ERR!   mongodb@"3.6.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional mongodb@"^5.2.0" from typeorm@0.3.16
npm ERR! node_modules/typeorm
npm ERR!   typeorm@"0.3.16" from the root project
npm ERR!   peer typeorm@"^0.3.0" from @nestjs/typeorm@9.0.1
npm ERR!   node_modules/@nestjs/typeorm
npm ERR!     @nestjs/typeorm@"9.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: mongodb@5.6.0
npm ERR! node_modules/mongodb
npm ERR!   peerOptional mongodb@"^5.2.0" from typeorm@0.3.16
npm ERR!   node_modules/typeorm
npm ERR!     typeorm@"0.3.16" from the root project
npm ERR!     peer typeorm@"^0.3.0" from @nestjs/typeorm@9.0.1
npm ERR!     node_modules/@nestjs/typeorm
npm ERR!       @nestjs/typeorm@"9.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/ff8743/cafb3d/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/ff8743/cafb3d/cache/others/npm/_logs/2023-06-13T06_59_14_010Z-debug-0.log

@kamilmysliwiec kamilmysliwiec merged commit c288902 into master Jun 13, 2023
3 of 5 checks passed
@delete-merged-branch delete-merged-branch bot deleted the renovate/supertest-6.x branch June 13, 2023 06:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant