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.version from 4.10.0 to 4.11.0 #2535

Merged
merged 1 commit into from Dec 29, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 29, 2022

Bumps mockito.version from 4.10.0 to 4.11.0.
Updates mockito-core from 4.10.0 to 4.11.0

Release notes

Sourced from mockito-core's releases.

v4.11.0

Changelog generated by Shipkit Changelog Gradle Plugin

4.11.0

Commits

Updates mockito-junit-jupiter from 4.10.0 to 4.11.0

Release notes

Sourced from mockito-junit-jupiter's releases.

v4.11.0

Changelog generated by Shipkit Changelog Gradle Plugin

4.11.0

Commits

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)

Bumps `mockito.version` from 4.10.0 to 4.11.0.

Updates `mockito-core` from 4.10.0 to 4.11.0
- [Release notes](https://github.com/mockito/mockito/releases)
- [Commits](mockito/mockito@v4.10.0...v4.11.0)

Updates `mockito-junit-jupiter` from 4.10.0 to 4.11.0
- [Release notes](https://github.com/mockito/mockito/releases)
- [Commits](mockito/mockito@v4.10.0...v4.11.0)

---
updated-dependencies:
- dependency-name: org.mockito:mockito-core
  dependency-type: direct:development
  update-type: version-update:semver-minor
- dependency-name: org.mockito:mockito-junit-jupiter
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: In Progress Use to signal this issue is actively worked on. Type: Dependency Upgrade Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only. labels Dec 29, 2022
@dependabot dependabot bot added this to the Release 4.7.0 milestone Dec 29, 2022
@smcvb smcvb self-assigned this Dec 29, 2022
Copy link
Member

@smcvb smcvb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me 👍

@smcvb smcvb merged commit f721584 into master Dec 29, 2022
@smcvb smcvb added Status: Resolved Use to signal that work on this issue is done. and removed Status: In Progress Use to signal this issue is actively worked on. labels Dec 29, 2022
@dependabot dependabot bot deleted the dependabot/maven/mockito.version-4.11.0 branch December 29, 2022 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Dependency Upgrade Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant