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 4.3.0 to 4.3.1 #23196

Merged
merged 2 commits into from Jan 26, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 25, 2022

Bumps mockito-core from 4.3.0 to 4.3.1.

Release notes

Sourced from mockito-core's releases.

v4.3.1

Changelog generated by Shipkit Changelog Gradle Plugin

4.3.1

Commits

Dependabot compatibility score

You can trigger a rebase of this PR 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-core](https://github.com/mockito/mockito) from 4.3.0 to 4.3.1.
- [Release notes](https://github.com/mockito/mockito/releases)
- [Commits](mockito/mockito@v4.3.0...v4.3.1)

---
updated-dependencies:
- dependency-name: org.mockito:mockito-core
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the area/dependencies Pull requests that update a dependency file label Jan 25, 2022
@quarkus-bot quarkus-bot bot added area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/platform Issues related to definition and interaction with Quarkus Platform labels Jan 25, 2022
@famod
Copy link
Member

famod commented Jan 25, 2022

The new BOM has been fixed in this patch release, so I switched to it. /cc @gsmet @aloubyansky

@gsmet
Copy link
Member

gsmet commented Jan 25, 2022

@famod have you checked the BOM doesn't contain anything we don't want (parents included)?

@famod
Copy link
Member

famod commented Jan 25, 2022

@gsmet of course, only mockito dependencies: https://search.maven.org/artifact/org.mockito/mockito-bom/4.3.1/pom

They do seem to generate it though, via Gradle. So there is no guarantee nothing slips in but then again we have this problem with all BOMs I guess...

@gsmet gsmet merged commit cb04a71 into main Jan 26, 2022
@quarkus-bot quarkus-bot bot added this to the 2.8 - main milestone Jan 26, 2022
@dependabot dependabot bot deleted the dependabot/maven/org.mockito-mockito-core-4.3.1 branch January 26, 2022 07:02
@gsmet gsmet modified the milestones: 2.8 - main, 2.7.0.Final Jan 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependencies Pull requests that update a dependency file area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/platform Issues related to definition and interaction with Quarkus Platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants