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

Bump mockito-core from 2.23.0 to 3.5.13 #115

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps mockito-core from 2.23.0 to 3.5.13.

Release notes

Sourced from mockito-core's releases.

v3.5.13

Release notes were automatically generated by Shipkit

3.5.13

v3.5.12

Release notes were automatically generated by Shipkit

3.5.12

v3.5.11

Release notes were automatically generated by Shipkit

3.5.11

v3.5.10

Release notes were automatically generated by Shipkit

3.5.10

v3.5.9

Release notes were automatically generated by Shipkit

3.5.9

v3.5.8

Release notes were automatically generated by Shipkit

3.5.8

v3.5.7

Release notes were automatically generated by Shipkit

3.5.7

Commits
  • 0ddbcb6 3.5.13 release (previous 3.5.12) + release notes updated by CI build 4808
  • 079e847 Use single version for strict dependency check in mockito-android (#2053)
  • e338d91 3.5.12 release (previous 3.5.11) + release notes updated by CI build 4800
  • 6ec033c Update Byte Buddy to 1.10.15 (#2050)
  • 5a664cf 3.5.11 release (previous 3.5.10) + release notes updated by CI build 4792
  • ce996dc [ci maven-central-release] Merge pull request #2046 from mockito/include-synt...
  • 4a40f58 Do not exclude synthetic constructors from instrumentation. Fixes #2040.
  • b6ae6cf 3.5.10 release (previous 3.5.9) + release notes updated by CI build 4773
  • 893e2f4 [ci maven-central-release] Merge pull request #2034 from mockito/explicit-esc...
  • 093d527 Escape mock during method dispatch on mock to avoid premature garbage collect...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [mockito-core](https://github.com/mockito/mockito) from 2.23.0 to 3.5.13.
- [Release notes](https://github.com/mockito/mockito/releases)
- [Commits](mockito/mockito@v2.23.0...v3.5.13)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Sep 25, 2020
@codecov-commenter
Copy link

Codecov Report

Merging #115 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #115   +/-   ##
=======================================
  Coverage   16.94%   16.94%           
=======================================
  Files          94       94           
  Lines        2018     2018           
  Branches      192      192           
=======================================
  Hits          342      342           
  Misses       1658     1658           
  Partials       18       18           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d75cec1...e4cfdb1. Read the comment docs.

@dependabot-preview
Copy link
Contributor Author

Superseded by #119.

@dependabot-preview dependabot-preview bot deleted the dependabot/gradle/org.mockito-mockito-core-3.5.13 branch October 20, 2020 04:44
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