Update dependency org.mockito:mockito-core to v5.18.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.mockito:mockito-core	5.13.0 -> 5.18.0

---

Release Notes

mockito/mockito (org.mockito:mockito-core)

v5.18.0

Compare Source

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.18.0

• 2025-05-20 - 5 commit(s) by Eugene Platonov, Patrick Doyle, Tim van der Lippe, dependabot[bot]
• Make vararg checks Scala friendly (for mockito-scala) (#​3651)
• For UnfinishedStubbingException, suggest the possibility of another thread (#​3636)
• UnfinishedStubbingException ought to suggest the possibility of another thread (#​3635)

v5.17.0

Compare Source

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.17.0

• 2025-04-04 - 7 commit(s) by Adrian Roos, Andre Kurait, Jan Ouwens, Rafael Winterhalter, Taeik Lim, Thach Le, Tim van der Lippe
• Fixes #​3631: Fix broken banner image link (#​3632)
• Banner image is broken (#​3631)
• Update exception message with mockito-inline (#​3628)
• Clarify structure of commit messages (#​3626)
• Fixes #​3622: MockitoExtension fails cleanup when aborted before setup (#​3623)
• MockitoExtension fails cleanup when aborted before setup (#​3622)
• Since mockito-inline has been removed, the exception messages with mockito-inline should be modified. (#​3621)
• Fixes #​3171: Fall back to Throwable Location strategy on Android (#​3619)
• Fixes #​3615 : broken links to javadoc.io (#​3616)
• Broken links to javadoc.io (#​3615)
• Mocks are not working on particular devices after update Android SDK from 33 to 34 (#​3171)

v5.16.1

Compare Source

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.16.1

• 2025-03-15 - 3 commit(s) by Adrian Roos, Jérôme Prinet, Rafael Winterhalter
• Remove Arrays.asList from critical stubbing path in GenericMetadataSu… (#​3610)
• Rework of injection strategy in the context of modules (#​3608)
• Adjust inline mocking snippet to allow task relocatability (#​3606)
• Inline mocking configuration snippet for Gradle should allow task relocatability (#​3605)

v5.16.0

Compare Source

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.16.0

• 2025-03-03 - 10 commit(s) by Brice Dutheil, Rafael Winterhalter, TDL, dependabot[bot]
• Add support for including module-info in Mockito. (#​3597)
• Bump com.gradle.develocity from 3.19 to 3.19.1 (#​3579)
• Bump org.assertj:assertj-core from 3.27.2 to 3.27.3 (#​3577)
• Bump com.diffplug.spotless:spotless-plugin-gradle from 7.0.1 to 7.0.2 (#​3574)
• Bump com.diffplug.spotless:spotless-plugin-gradle from 6.25.0 to 7.0.1 (#​3571)
• Bump org.assertj:assertj-core from 3.27.1 to 3.27.2 (#​3569)
• Tweaks documentation on mockito agent config for maven (#​3568)
• Adds --info to diagnose closeAndReleaseStagingRepositories issues (#​3567)
• Refine reflection when calling management factory (#​3566)
• Avoid warning when dynamic attach is enabled (#​3551)

v5.15.2

Compare Source

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.15.2

• 2025-01-02 - 2 commit(s) by Brice Dutheil, dependabot[bot]
• Fix javadoc publication (#​3561)
• Bump org.assertj:assertj-core from 3.27.0 to 3.27.1 (#​3560)
• The release job is failed again (#​3542)

v5.14.2

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.14.2

• 2024-10-15 - 12 commit(s) by Brice Dutheil, Rafael Winterhalter, dependabot[bot]
• Fix #​3466 nexus publishing configuration (#​3470)
• Bump org.jetbrains.kotlin:kotlin-stdlib from 2.0.20 to 2.0.21 (#​3468)
• Bump bytebuddy from 1.15.3 to 1.15.4 (#​3467)
• Missing 5.14.2 release (#​3466)
• chore: Tests whether JVM warnings / messages on dynamic attach (#​3462)
• Bump junit-jupiter from 5.11.1 to 5.11.2 (#​3461)
• Renames extension modules with mockito- prefix (#​3460)
• Avoid attach warning if Byte Buddy is configured for command-line attach. (#​3459)
• Bump org.shipkit:shipkit-auto-version from 2.0.10 to 2.0.11 (#​3458)
• Bump junit-jupiter from 5.11.0 to 5.11.1 (#​3455)
• Move root project to dedicated core folder (#​3444)
• Bump biz.aQute.bnd:biz.aQute.bnd.gradle from 6.4.0 to 7.0.0 (#​3136)

v5.14.1

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.14.1

• 2024-09-30 - 2 commit(s) by Brice Dutheil, dependabot[bot]
• fix: gradle mockitoAgent configuration should not be transitive (#​3454)
• Bump bytebuddy from 1.15.2 to 1.15.3 (#​3452)
• Allow for installing a Java agent within the Mockito jar, without exposing Byte Buddy's attach mechanism. (#​3437)

v5.14.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.14.0

• 2024-09-27 - 9 commit(s) by Ali-Hassan, Brice Dutheil, David Saff, Rafael Winterhalter, dependabot[bot]
• Bump org.junit.platform:junit-platform-launcher from 1.11.0 to 1.11.1 (#​3451)
• Bump bytebuddy from 1.15.1 to 1.15.2 (#​3450)
• Update Documentation of ArgumentCaptor.java (#​3448)
• Split subprojects (#​3447)
• Separate extensions from integration tests (#​3443)
• Bump org.eclipse.platform:org.eclipse.osgi from 3.20.0 to 3.21.0 (#​3440)
• Bump com.gradle.enterprise from 3.18 to 3.18.1 (#​3439)
• Allow for installing a Java agent within the Mockito jar, without exposing Byte Buddy's attach mechanism. (#​3437)
• Bump bytebuddy from 1.15.0 to 1.15.1 (#​3434)
• Fixes #​3419: Disable mocks with an error message (#​3424)
• Accessing a mock after clearInlineMocks could provide much more useful error message. (#​3419)

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.