fix(deps): Update dependency org.mockito:mockito-core to v5

[cq-bot]

This PR contains the following updates:

Package	Type	Update	Change
org.mockito:mockito-core	dependencies	major	3.12.4 -> 5.4.0

---

Release Notes

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

v5.4.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.4.0

• 2023-06-18 - 22 commit(s) by Alexander von Trostorff, Andriy Redko, Benoit Maggi, Chris Povirk, DerFrZocker, Nicolas Ot, Tim van der Lippe, dependabot[bot], ellaella12
• Bump versions.errorprone from 2.19.1 to 2.20.0 (#​3041)
• Bump org.eclipse.platform:org.eclipse.osgi from 3.18.300 to 3.18.400 (#​3038)
• Bump com.google.auto.service:auto-service from 1.1.0 to 1.1.1 (#​3036)
• Bump com.github.ben-manes.versions from 0.46.0 to 0.47.0 (#​3034)
• Bump kotlinVersion from 1.8.21 to 1.8.22 (#​3033)
• Documentation about MockMakers slightly outdated in some places. Fixes #​3031 (#​3032)
• Documentation about MockMakers slightly outdated in some places (#​3031)
• Bump versions.bytebuddy from 1.14.4 to 1.14.5 (#​3025)
• Edit DoAnswerStyleStubbing.isSet() to return true if there are answers (#​3020)
• Bump com.diffplug.spotless from 6.18.0 to 6.19.0 (#​3018)
• Bump com.google.auto.service:auto-service from 1.0.1 to 1.1.0 (#​3017)
• Bump versions.errorprone from 2.18.0 to 2.19.1 (#​3009)
• Fix @Mock(serializable = true) for parameterized types. (#​3007)
• Add varargs changes to ArgumentMatchers#any() JavaDoc
  (#​3003)
• Mockito 5 any() does not match a vararg int[] argument anymore. I need to use any(int[].class) to get the ArgumentMatcher to work (#​2998)
• Bump com.google.googlejavaformat:google-java-format from 1.16.0 to 1.17.0 (#​2996)
• Remove redundant double "now" in JavaDocs for mock without class (#​2994)
• Bump org.junit.platform:junit-platform-launcher from 1.9.2 to 1.9.3 (#​2993)
• Bump versions.junitJupiter from 5.9.2 to 5.9.3 (#​2992)
• Provide a variant of assertArg that works well with checked exceptions (#​2991)
• Bump kotlinVersion from 1.8.10 to 1.8.21 (#​2990)
• Fix #​2915 Forbid spy on mocked interface (#​2989)
• Bump net.ltgt.gradle:gradle-errorprone-plugin from 3.0.1 to 3.1.0 (#​2987)
• @Mock(serializable = true) no longer works with parameterized types (#​2979)
• Bug with @​InjectMocks in 5.3.0 (#​2978)
• �Function name is incorrect. (#​2955)
• Verify on Spy Interface incorrect count of actual invocation (#​2915)
• Only run injection once (#​2603)
• mockito-core MockitoAnnotations::openMocks initializes class twice if said class has super class (#​2602)

v5.3.1

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.3.1

• 2023-04-21 - 2 commit(s) by Rafael Winterhalter, jfrantzius
• Fixes 2972: Weakens visibility constraint (#​2983)
• Bugfix 2974 fix npe (#​2976)
• Fix for #​2958 eliminates CCE but leads to NPE (#​2974)
• Spying objects not working properly since 5.3.0 (#​2972)

v5.3.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.3.0

• 2023-04-11 - 14 commit(s) by Krzysztof Krasoń, Maciej Walkowiak, Rafael Winterhalter, Wesley Tsai, dependabot[bot], jfrantzius
• Bump com.diffplug.spotless from 6.17.0 to 6.18.0 (#​2967)
• Bump versions.bytebuddy from 1.14.3 to 1.14.4 (#​2966)
• Adds withoutAnnotations parameter to @Mock (#​2965)
• Fix ClassCastException (#​2962)
• Bump org.codehaus.groovy:groovy from 3.0.16 to 3.0.17 (#​2959)
• ClassCastException when combining InjectMocks with generified Mock field (#​2958)
• Bump versions.bytebuddy from 1.14.2 to 1.14.3 (#​2950)
• Add ArgumentMatchers#assertArg method. (#​2949)
• Fixes 2947: correct visibility check to respect nestmates (#​2948)
• spy does not initialize objects fully with InstrumentationMemberAccessor (#​2947)
• Fixes #​2877: removed mockito-inline as subproject and actual subproject (#​2945)
• #​2934 throw exception on multiple matches by type if cannot be reduce… (#​2942)
• Bump org.eclipse.platform:org.eclipse.osgi from 3.18.200 to 3.18.300 (#​2941)
• Bump com.diffplug.spotless from 6.16.0 to 6.17.0 (#​2940)
• Bump org.codehaus.groovy:groovy from 3.0.15 to 3.0.16 (#​2939)
• Bump versions.bytebuddy from 1.14.1 to 1.14.2 (#​2938)
• Feature suggestion: TerminalMockCandidateFilter should report error when more than one candidate left (#​2934)
• Mockito-inline dependency after upgrade 5.0.0 (#​2877)
• Assertions on parameters during verification (#​2285)

v5.2.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.2.0

• 2023-03-09 - 25 commit(s) by Andriy Redko, Iulian Dragos, Roberto Trunfio, Róbert Papp, dependabot[bot], jfrantzius, tobiasbaum
• Fixes 2933: IOUtils does not depend on platform encoding any more (#​2935)
• Execution with mockito-inline fails on platforms with EBCDIC as default encoding (#​2933)
• Bump io.github.gradle-nexus:publish-plugin from 1.2.0 to 1.3.0 (#​2932)
• Bump versions.bytebuddy from 1.14.0 to 1.14.1 (#​2931)
• Bump com.diffplug.spotless from 6.15.0 to 6.16.0 (#​2930)
• Bump com.google.googlejavaformat:google-java-format from 1.15.0 to 1.16.0 (#​2928)
• Bump io.github.gradle-nexus:publish-plugin from 1.1.0 to 1.2.0 (#​2924)
• Feature 2921 generic types (#​2923)
• Bump com.github.ben-manes.versions from 0.45.0 to 0.46.0 (#​2922)
• Use generic type information in TypeBasedCandidateFilter to circumvent type erasure (#​2921)
• Make project relocatable by using relative paths in the OSGi test task (#​2920)
• Cache misses due to OSGi tests referencing absolute paths (#​2919)
• Bump versions.bytebuddy from 1.13.0 to 1.14.0 (#​2918)
• Bump gradle/wrapper-validation-action from 1.0.5 to 1.0.6 (#​2917)
• Bump com.diffplug.spotless from 6.14.1 to 6.15.0 (#​2913)
• Bump versions.bytebuddy from 1.12.23 to 1.13.0 (#​2912)
• Bump ru.vyarus.animalsniffer from 1.6.0 to 1.7.0 (#​2911)
• Bump org.codehaus.groovy:groovy from 3.0.14 to 3.0.15 (#​2910)
• Fixes #​2905 : ThreadLocal classes can be mocked. (#​2908)
• StackOverflow while mocking a ThreadLocal on Mockito 5.1.1 (#​2905)
• Fix most Gradle warnings in build (#​2904)
• Android CI improvements, improves #​2892 (#​2903)
• Bump com.diffplug.spotless from 6.14.0 to 6.14.1 (#​2902)
• Bump versions.bytebuddy from 1.12.22 to 1.12.23 (#​2901)
• CI on Android API level 33 for Java 11 compatibility testing (#​2899)
• Bump kotlinVersion from 1.8.0 to 1.8.10 (#​2897)
• Bump com.github.ben-manes.versions from 0.44.0 to 0.45.0 (#​2895)
• Simplify and modernize Android Test module. (#​2894)
• Set up Android Github Action pipeline. Fixes #​2892 (#​2893)

v5.1.1

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.1.1

• 2023-01-30 - 1 commit(s) by Andriy Redko
• StackWalker.Option not found on Mockito 5.1.0 (#​2891)
• StackWalker.Option not found on Mockito 5.1.0 (#​2890)

v5.1.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

5.1.0

• 2023-01-29 - 12 commit(s) by Andriy Redko, Ashley, Róbert Papp, Stephan Schroevers, Tim te Beek, dependabot[bot]
• Fixes some mistakes and missing details in documentation (#​2889)
• Bump com.diffplug.spotless from 6.13.0 to 6.14.0 (#​2888)
• Clean up JDK-8 related code (#​2883)
• Feat: reified mock overloads (#​2882)
• Clean up JDK-8 related code (#​2879)
• Bump assertj-core from 3.24.1 to 3.24.2 (#​2875)
• Make sure the tests use mock maker with intended member accessor (#​2872)
• Bump com.diffplug.spotless from 6.12.1 to 6.13.0 (#​2871)
• Remove broken link from CONTRIBUTING.md (#​2870)
• Update outdated badge 3.x to 5.x (#​2869)
• Broken link in CONTRIBUTING.md (#​2868)
• Set current version to 5.x in README and highlight changes (#​2867)
• Annotate Mockito#{mock,spy}(T... reified) with @SafeVarargs (#​2866)
• Make sure the tests use mock maker with intended member accessor (#​2855)
• Improve examples for InOrder (#​2843)

v5.0.0

Mockito 5: prepare for future JDK versions

For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API.
Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker.
Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working.

Switch the default mockmaker to mockito-inline

Back in Mockito 2.7.6, we published a new mockmaker based on the "inline bytecode" principle.
This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery.
As a comparison, the subclass mockmaker generates "real" subclasses for mocks, to mimic the same behavior.
While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes.
For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass.

Massive thanks to community member @​reta who implemented this change.

Note: this does not affect mockito-android nor testing on Android.

When should I still be using the subclass mockmaker?

There are legitimate remaining use cases for the subclass mockmaker.
For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice.
Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility.
Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+.
We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker.

If you want to use the subclass mockmaker instead, you can use the new mockito-subclass artifact (published on Maven Central along with all our other artifacts).

Update the minimum supported Java version to 11

Mockito 4 supports Java 8 and above.
Similar to other open source projects, we are moving away from JDK 8 and to newer versions.
The primary reason for moving away from JDK 8 is the increasing maintenance costs with keeping our own infrastructure working.
Lately we have been running into more and more JDK 8 breakages.
Additionally, while we want to support the newest JDK API's, our current solution to support both JDK 8 and newer versions causes issues with the SecurityManager.
Since we want Mockito to work on the newest version and more and more businesses adopting JDK 11, we have decided to make the switch as well.

Massive thanks to community member @​reta who implemented this change.

What should I do if I still run JDK 8?

For JDK 8 and below, you can keep on using Mockito 4.
This is similar to if you are using JDK 6, for which you can keep on using Mockito 2.
The changes in Mockito 5 (for now) are primarily focused on the latest JDK versions, which means the API differences between Mockito 4 and 5 are minimal.
However, over time this will most likely widen, so we do recommend adopting JDK 11 in the future.

New type() method on ArgumentMatcher

One of our most used public API's for customizing Mockito is the ArgumentMatcher interface.
The interface allows you to define a custom matcher, which you can pass into method arguments to provide more targeted matches.
One major shortcoming of the ArgumentMatcher was the lack of varargs support.
There were many, many issues filed related to varargs and Mockito unable to handle them.

Community member @​big-andy-coates put in a lot of effort to come up with an appropriate solution, including fully implementing and comparing 2 approaches.
Ultimately, we decided that introducing a new type() method on ArgumentMatcher is the best solution.
As a result, it is now possible to update your custom matchers to implement varargs support, if you so desire.
Note that ArgumentMatcher is still a @FunctionalInterface and can therefore still be written as a lambda.

Massive thanks to community member @​big-andy-coates who implemented this change.

What is the effect of this new method?

For varargs methods, there was previously a way to only match zero arguments, or two or more arguments, by using the exact number of matchers, i.e.

long call(String... args);

// Will match calls with exactly zero arguments:
when(mock.call()).thenReturn(0L);

// Will match calls with exactly two arguments:
when(mock.call(any(), any())).thenReturn(0L);

But following the pattern to match exactly one argument:

when(mock.call(any())).thenReturn(0L);

doesn't work, as any is "vararg aware", so Mockito matched the any against each element of the varargs parameter, meaning it will match any number of arguments, i.e. the above would of matched all of these:

mock.call();
mock.call("a");
mock.call("a", "b");

With the new type method, it's now possible to differentiate matching calls with any exact number of arguments, or to match any number of arguments.

// Match any number of arguments:
when(mock.call(any(String[].class))).thenReturn(1L);
// Match invocations with no arguments:
when(mock.call()).thenReturn(1L);
// Match invocations with exactly one argument:
when(mock.call(any())).thenReturn(1L);
// Alternative to match invocations with exactly one argument:
when(mock.call(any(String.class))).thenReturn(1L);
// Match invocations with exactly two arguments:
when(mock.call(any(), any())).thenReturn(1L);

Therefore, if you want to match 0 or more arguments, use any(String[].class).
If you want to match an exact number of arguments, use any(String.class) (and specify as many any matchers as arguments you want to match on).

In a similar fashion, the behavior of ArgumentCaptor.forClass has changed as well.
If you want to capture all arguments, use an ArgumentCaptor for String[], otherwise String:

// Will capture 1 string
@&#8203;Captor private ArgumentCaptor<String> captor;
// Will capture all strings
@&#8203;Captor private ArgumentCaptor<String[]> captor;

For more information, see the description and conversation in pull request 2835 and pull request 2807.

At the same time, ArgumentCaptor is now fully type-aware.
This allows for capturing specific subclasses on a generic method:

// Given:
int simpleMethod(Collection<?> arg);

// When:
mock.simpleMethod(Set.of());
mock.simpleMethod(List.of());

// Then:
ArgumentCaptor<Collection<?>> captor = ArgumentCaptor.forClass(List.class);
verify(mock).simpleMethod(captor.capture());
assertThat(captor.getAllValues()).containsExactly(List.of());

Do I need to implement this new method?

No, you don't need to.
Mockito 5 declares a default implementation, returning Void.type as the type of an ArgumentMatcher.
This essentially means that Mockito will not consider the type when handling varargs.
However, if you do return a specific type, Mockito will consider this when matching arguments.
As a result, this new method is not a source-breaking change, but is a bytecode-breaking change.
All code working on Mockito 4 should work as-is when recompiled with Mockito 5.

v4.11.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.11.0

• 2022-12-28 - 1 commit(s) by Andy Coates
• Improve vararg handling: approach 2 (#​2807)
• Mocking varargs method with any(String[].class) doesn't work as expected (#​2796)
• (Argument)Matchers regression from 1.10.19 to 2.18.3 for varargs (#​1498)
• Cannot verify varargs parameter as an array (#​1222)
• ArgumentCaptor can't capture varargs-arrays (#​584)
• Verification of an empty varargs call fails when isNotNull() is used (#​567)

v4.10.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.10.0

• 2022-12-14 - 13 commit(s) by Andrei Solntsev, Andriy Redko, Andy Coates, Christopher Lambert, Marcono1234, Vladimir Glinskikh, dependabot[bot]
• Add new artifact mockito-subclass (to use mock-maker-subclass MockMaker) (#​2821)
• Bump gradle from 7.5.1 to 7.6 (#​2817)
• Fix incorrect Javadoc inline tag for MockitoJUnitRunner (#​2816)
• Bump shipkit-auto-version from 1.2.1 to 1.2.2 (#​2811)
• Bump com.github.ben-manes.versions from 0.42.0 to 0.44.0 (#​2810)
• Bump kotlinVersion from 1.7.21 to 1.7.22 (#​2809)
• Bump junit from 1.1.3 to 1.1.4 (#​2806)
• Simplify MatcherApplicationStrategy (#​2803)
• Bump kotlinVersion from 1.7.10 to 1.7.21 (#​2801)
• Bump espresso-core from 3.4.0 to 3.5.0 (#​2800)
• Bump versions.bytebuddy from 1.12.16 to 1.12.19 (#​2799)
• Upgrade errorprone from 2.14.0 to 2.16 (#​2794)
• automatically detect class to mock (#​2779)

v4.9.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.9.0

• 2022-11-14 - 6 commit(s) by Andrei Solntsev, Rafael Winterhalter, Rick Ossendrijver, dependabot[bot]
• Upgrade objenesis 3.2 -> 3.3 (#​2784)
• Upgrade objenesis 3.2 -> 3.3 (#​2783)
• Avoids clearing stale weak entries from critical code segments. (#​2780)
• bump gradle from 7.3.1 to 7.5.1 (#​2776)
• Bump gradle/wrapper-validation-action from 1.0.4 to 1.0.5 (#​2775)
• Bump gradle-errorprone-plugin from 2.0.2 to 3.0.1 (#​2770)
• Bump junit-platform-launcher from 1.9.0 to 1.9.1 (#​2768)

v4.8.1

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.8.1

• 2022-10-17 - 6 commit(s) by andrepaschoal, dependabot[bot]
• Possible fix #​2765: Add task to download package-list file from java as element-list (#​2766)
• JavaDoc warning is blocking all pull requests (#​2765)
• Bump versions.junitJupiter from 5.9.0 to 5.9.1 (#​2758)
• Bump groovy from 3.0.12 to 3.0.13 (#​2756)
• Bump com.diffplug.spotless from 6.10.0 to 6.11.0 (#​2753)
• Bump org.eclipse.osgi from 3.18.0 to 3.18.100 (#​2751)
• Bump versions.bytebuddy from 1.12.14 to 1.12.16 (#​2747)

v4.8.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.8.0

• 2022-09-07 - 10 commit(s) by Alex, James Baker, Johannes Spangenberg, Kurt Alfred Kluever, Rafael Winterhalter, Thibault Helsmoortel, dependabot[bot]
• GitHub Workflows security hardening (#​2744)
• Assign GlobalConfiguration initializer to unused variable (#​2742)
• Bump com.diffplug.spotless from 6.9.1 to 6.10.0 (#​2738)
• Drop varargs collector before invoking a user method. (#​2736)
• Bump versions.bytebuddy from 1.12.13 to 1.12.14 (#​2734)
• Remove useless thrown exception from constructor (#​2732)
• TypeSafeMatching no longer iterates over class methods inefficiently (#​2729)
• Fixes #​2720: Use StackWalker on Java 9+ to create Locations (#​2723)
• LocationImpl adds performance overheads due to instantiating a stack trace (#​2720)
• Fixes #​2626 : Introduce MockSettings.mockMaker (#​2701)
• Introduce option to disable inline-mock-maker for a specific instance (#​2626)

v4.7.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.7.0

• 2022-08-13 - 33 commit(s) by 1988123, Andy Coates, Chen Ni, Marius Lichtblau, Nikita Koselev. Developer Advocate, Open Source Ally, Rafael Winterhalter, dependabot[bot], dstango, fishautumn, heqiang
• Bump com.diffplug.spotless from 6.9.0 to 6.9.1 (#​2725)
• Bump versions.bytebuddy from 1.12.12 to 1.12.13 (#​2719)
• Fix Javadoc for Mockito. (#​2718)
• Bump com.diffplug.spotless from 6.8.0 to 6.9.0 (#​2717)
• Fix a typo in comment of InternalRunner.java (#​2715)
• Bump junit-platform-launcher from 1.8.2 to 1.9.0 (#​2713)
• Bump versions.junitJupiter from 5.8.2 to 5.9.0 (#​2712)
• Bump groovy from 3.0.11 to 3.0.12 (#​2711)
• Bump shipkit-auto-version from 1.2.0 to 1.2.1 (#​2709)
• Bump kotlinVersion from 1.7.0 to 1.7.10 (#​2705)
• Bump com.diffplug.spotless from 6.7.2 to 6.8.0 (#​2699)
• Bump versions.bytebuddy from 1.12.11 to 1.12.12 (#​2695)
• Makes error message less misleading and points to github for help. Issue #​2692 (#​2693)
• Misleading error message when mocking and a class (of a parameter) is not found (#​2692)
• Bump kotlinx-coroutines-core from 1.6.1-native-mt to 1.6.3-native-mt (#​2691)
• Bump versions.bytebuddy from 1.12.10 to 1.12.11 (#​2690)
• Fixes #​2679 : Update Javadoc (#​2689)
• Bump org.eclipse.osgi from 3.17.200 to 3.18.0 (#​2688)
• RETURNS_SELF: Avoids returning mock when mock type is assignable to method return type, but method return type is Object. (#​2687)
• RETURNS_SELF breaks methods with generic return type (#​2686)
• Fix #​2616 wrong stub for nested static (#​2685)
• Bump com.diffplug.spotless from 6.7.0 to 6.7.2 (#​2684)
• Avoids starting mocks "half-way" if a superclass constructor is mocked but an unmocked subclass is initiated. (#​2682)
• Fix typo (#​2681)
• Update javadoc of Strictness.STRICT_STUBS (#​2679)
• Bump kotlinVersion from 1.6.21 to 1.7.0 (#​2677)
• Bump biz.aQute.bnd.builder from 6.3.0 to 6.3.1 (#​2675)
• Bump biz.aQute.bnd.gradle from 6.3.0 to 6.3.1 (#​2674)
• Bump com.diffplug.spotless from 6.6.1 to 6.7.0 (#​2672)
• update CONTRIBUTING.md - stackoverflow (#​2671)
• stackoverflow.com is a non-actionable text, to be replaced with a hyperlink (#​2670)
• Fix typos (#​2669)
• Bump biz.aQute.bnd.gradle from 6.2.0 to 6.3.0 (#​2666)
• Bump biz.aQute.bnd.builder from 6.2.0 to 6.3.0 (#​2665)
• Improve Varargs handling in AdditionalAnswers (#​2664)
• Bump appcompat from 1.4.1 to 1.4.2 (#​2663)
• Varargs methods cause ClassCastException in AnswerFunctionalInterfaces (#​2644)
• Mock static class seems records wrong invocations if called nested method throws exception (#​2616)

v4.6.1

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.6.1

• 2022-06-02 - 6 commit(s) by Andy Coates, Chen Ni, dependabot[bot]
• Bump material from 1.6.0 to 1.6.1 (#​2662)
• Bump core-ktx from 1.7.0 to 1.8.0 (#​2661)
• Bump groovy from 3.0.10 to 3.0.11 (#​2660)
• Fix for Issue2656 (#​2659)
• Bump assertj-core from 3.22.0 to 3.23.1 (#​2658)
• Regression? Strictness set in @MockitoSettings ignored after upgrade from 4.5.1 to 4.6.0 (#​2656)
• Fix typo (#​2655)

v4.6.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.6.0

• 2022-05-27 - 14 commit(s) by Hervé Boutemy, K. Siva Prasad Reddy, Rafael Winterhalter, dependabot[bot]
• Bump shipkit-changelog from 1.1.15 to 1.2.0 (#​2654)
• Bump versions.errorprone from 2.13.1 to 2.14.0 (#​2653)
• Bump shipkit-auto-version from 1.1.20 to 1.2.0 (#​2651)
• Fixes #​2648 : Add support for customising strictness via @​Mock annotation and MockSettings (#​2650)
• Any way to enable Strict Stubbing when using Mockito.mock() without using @​Mock? (#​2648)
• Reintroduce inheriting type annotations from interfaces if only one interface is mocked, including additional interfaces. (#​2645)
• Bump com.diffplug.spotless from 6.6.0 to 6.6.1 (#​2643)
• fix Reproducible Build issue (#​2642)
• Bump com.diffplug.spotless from 6.5.2 to 6.6.0 (#​2641)
• Mockito mock of interfaces lost annotation information (#​2640)
• Bump material from 1.5.0 to 1.6.0 (#​2637)
• Bump com.diffplug.spotless from 6.5.1 to 6.5.2 (#​2636)
• Bump versions.bytebuddy from 1.12.9 to 1.12.10 (#​2635)
• Bump com.diffplug.spotless from 6.5.0 to 6.5.1 (#​2632)
• Bump com.diffplug.spotless from 6.4.2 to 6.5.0 (#​2631)

v4.5.1

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.5.1

• 2022-04-21 - 2 commit(s) by Jeremy Landis, dependabot[bot]
• Fixes #​2623: Use zulu distribution and java 11 for release GHA job (#​2624)
• Missing errorprone module for 4.5.0 in central as release was done with jdk 8 (#​2623)
• Bump kotlinVersion from 1.6.20 to 1.6.21 (#​2622)

Missing net.bytebuddy.utility.GraalImageCode exception

If you encounter any issues with missing ByteBuddy classes, make sure you are using ByteBuddy 1.12 or higher.

v4.5.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.5.0

• 2022-04-19 - 15 commit(s) by Andrei Silviu Dragnea, Rafael Winterhalter, Rick Ossendrijver, dependabot[bot]
• Bump versions.errorprone from 2.13.0 to 2.13.1 (#​2621)
• Bump versions.errorprone from 2.12.1 to 2.13.0 (#​2619)
• Groovy inline (#​2618)
• Bump actions/setup-java from 2 to 3 (#​2615)
• Bump versions.bytebuddy from 1.12.8 to 1.12.9 (#​2614)
• Support subclass mocks on Graal VM. (#​2613)
• Bump com.diffplug.spotless from 6.4.1 to 6.4.2 (#​2611)
• Bump kotlinx-coroutines-core from 1.6.0-native-mt to 1.6.1-native-mt (#​2609)
• Bump versions.errorprone from 2.10.0 to 2.12.1 (#​2608)
• Bump kotlinVersion from 1.6.10 to 1.6.20 (#​2607)
• Bump com.diffplug.spotless from 6.4.0 to 6.4.1 (#​2606)
• Bump com.diffplug.spotless from 6.3.0 to 6.4.0 (#​2605)
• Bump org.eclipse.osgi from 3.17.100 to 3.17.200 (#​2597)
• Deprecate ListUtil and Fields classes (#​2593)
• mockito-errorprone seems not compatible with ErrorProne 2.11.0 (#​2554)
• NullPointerException from Groovy metaclass methods when using mockito-inline (but not mockito-core) (#​2522)

v4.4.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.4.0

• 2022-03-08 - 16 commit(s) by Andrew Kozel, Brice Dutheil, Jean-Baptiste Mille, Mirko Alicastro, dependabot[bot]
• Bump groovy from 3.0.9 to 3.0.10 (#​2586)
• Bump google-java-format from 1.14.0 to 1.15.0 (#​2585)
• Bump actions/checkout from 2.4.0 to 3 (#​2582)
• Bump shipkit-auto-version from 1.1.19 to 1.1.20 (#​2580)
• Bump biz.aQute.bnd.builder from 6.1.0 to 6.2.0 (#​2579)
• Bump biz.aQute.bnd.gradle from 6.1.0 to 6.2.0 (#​2578)
• Adds a Google Java Format for JDK17 (#​2572)
• Clean up JUnit3 references (#​2570)
• Bump com.diffplug.spotless from 6.2.2 to 6.3.0 (#​2567)
• Bump google-java-format from 1.13.0 to 1.14.0 (#​2565)
• Bump versions.bytebuddy from 1.12.7 to 1.12.8 (#​2564)
• Bump com.diffplug.spotless from 6.2.1 to 6.2.2 (#​2562)
• Bump com.github.ben-manes.versions from 0.41.0 to 0.42.0 (#​2559)
• Bump com.diffplug.spotless from 6.2.0 to 6.2.1 (#​2556)
• Fixes #​2548 : Makes InOrder able to verify static methods (#​2549)
• [PR open] Add feature to verify static methods calls in order (#​2548)
• Fixes #​2201 : Fixed checking of declared exceptions. (#​2547)
• Calling getExceptionTypes() on concrete object that is used as interface doesn't return exception types from interface (#​2201)

v4.3.1

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.3.1

• 2022-01-25 - 1 commit(s) by Stefano Cordio
• Add mockito-core to the BOM (#​2550)

v4.3.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.3.0

• 2022-01-24 - 20 commit(s) by Andrew Kozel, John Pyeatt, Liam Miller-Cushon, Thomas Keller, Tim van der Lippe, dependabot[bot], temp-droid
• Fixes #​2489 : Fixed issue related to exceptions thrown from the nested spies (#​2546)
• Issue 2544 (#​2545)
• Bump versions.bytebuddy from 1.12.6 to 1.12.7 (#​2543)
• Bump com.diffplug.spotless from 6.1.2 to 6.2.0 (#​2542)
• Bump material from 1.4.0 to 1.5.0 (#​2541)
• Bump appcompat from 1.4.0 to 1.4.1 (#​2539)
• Bump com.diffplug.spotless from 6.1.1 to 6.1.2 (#​2536)
• Remove an @link (#​2535)
• Bump com.diffplug.spotless from 6.1.0 to 6.1.1 (#​2534)
• Bump com.github.ben-manes.versions from 0.40.0 to 0.41.0 (#​2533)
• Bump assertj-core from 3.21.0 to 3.22.0 (#​2531)
• Bump com.github.ben-manes.versions from 0.39.0 to 0.40.0 (#​2529)
• Bump com.diffplug.spotless from 6.0.5 to 6.1.0 (#​2527)
• Bump kotlinx-coroutines-core from 1.5.2-native-mt to 1.6.0-native-mt (#​2526)
• Bump versions.bytebuddy from 1.12.5 to 1.12.6 (#​2524)
• Bump com.diffplug.spotless from 6.0.4 to 6.0.5 (#​2520)
• Bump versions.bytebuddy from 1.12.4 to 1.12.5 (#​2519)
• Fixes #​2510: Remove ExpectedException from internal test suite (#​2518)
• Fix JavaDoc warnings and enforce zero errors in Gradle (#​2513)
• Remove ExpectedException from internal test suite (#​2510)
• Incomplete stack trace returned from spy inside another spy (#​2489)
• Introduce a BOM for Mockito's artifacts (closes #​2321) (#​2323)
• Provide a bill of materials (BOM) (#​2321)

v4.2.0

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.2.0

• 2021-12-16 - 21 commit(s) by Liam Miller-Cushon, Rafael Winterhalter, Tim van der Lippe, dependabot[bot], temp-droid
• Update ByteBuddy to 1.12.4 (#​2515)
• Bump kotlinVersion from 1.6.0 to 1.6.10 (#​2514)
• Add DoNotMock mention to main JavaDoc (#​2512)
• Replace ExpectedException in MissingInvocationInOrderCheckerTest (#​2511)
• Update Gradle to version 7.3.1 (#​2509)
• Fixes #​2497: Throw exception on invalid matchers for mockStatic (#​2506)
• Make sure interface types are initialized before inline mocking to avoid blocking code of static initializers. (#​2505)
• Bump org.eclipse.osgi from 3.17.0 to 3.17.100 (#​2504)
• Bump com.diffplug.spotless from 6.0.2 to 6.0.4 (#​2501)
• Bump com.diffplug.spotless from 6.0.1 to 6.0.2 (#​2498)
• ArgumentMatchers not working for Mockito.mockStatic (#​2497)
• Bump versions.bytebuddy from 1.12.2 to 1.12.3 (#​2496)
• Bump com.diffplug.spotless from 6.0.0 to 6.0.1 (#​2495)
• Remove the recommendation to import ArgumentMatchers methods using Mockito (#​2494)
• Bump versions.junitJupiter from 5.8.1 to 5.8.2 (#​2491)
• Bump junit-platform-launcher from 1.8.1 to 1.8.2 (#​2490)
• Fix typo 'DoNoMock' should be 'DoNotMock' (#​2487)
• Bump biz.aQute.bnd.gradle from 6.0.0 to 6.1.0 (#​2486)
• Bump biz.aQute.bnd.builder from 6.0.0 to 6.1.0 (#​2485)
• Bump versions.bytebuddy from 1.12.1 to 1.12.2 (#​2484)
• Bump google-java-format from 1.12.0 to 1.13.0 (#​2483)
• Add annotation to mark a type as DoNotMock (#​1833)

v4.1.0

Major new feature: @DoNotMock

You can now mark classes/interfaces with @org.mockito.DoNotMock to disallow mocking with Mockito. For more information, see our documentation: https://javadoc.io/doc/org.mockito/mockito-core/latest/org/mockito/DoNotMock.html

^{Changelog generated by Shipkit Changelog Gradle Plugin}

4.1.0

• 2021-11-19 - 20 commit(s) by Lars Vogel, Mikaël Francoeur, S.YAMAMOTO, Tim van der Lippe, dependabot[bot]
• Disable memory test (#​2480)
• Bump appcompat from 1.3.1 to 1.4.0 (#​2477)
• Bump kotlinVersion from 1.5.31 to 1.6.0 (#​2474)
• Bump versions.bytebuddy from 1.12.0 to 1.12.1 (#​2472)
• Bump com.diffplug.gradle.spotless from 4.5.1 to 6.0.0 (#​2471)
• Bump versions.bytebuddy from 1.11.22 to 1.12.0 (#​2469)
• Bump versions.errorprone from 2.9.0 to 2.10.0 (#​2466)
• Bump auto-service from 1.0 to 1.0.1 (#​2463)
• Bump actions/checkout from 2.3.5 to 2.4.0 (#​2462)
• Fixes #​2460: Remove a sentence commits to a particular version (#​2461)
• Clarify Javadoc of RETURNS_SMART_NULLS, default answer in Mockito 4.0.0? (#​2460)
• Bump versions.bytebuddy from 1.11.21 to 1.11.22 (#​2458)
• Updated readme with the latest Mockito version (#​2456)
• Bump core-ktx from 1.6.0 to 1.7.0 (#​2454)
• Bump google-java-format from 1.11.0 to 1.12.0 (#​2450)
• Bump versions.bytebuddy from 1.11.20 to 1.11.21 (#​2448)
• Use new CodeCov uploader (#​2447)
• Bump actions/checkout from 2.3.4 to 2.3.5 (#​2445)
• Fixes #​2389 : Parallel use of mocks with deep stubbing may lead to ConcurrentModificationException (#​2444)
• Bump versions.bytebuddy from 1.11.19 to 1.11.20 (#​2443)
• Parallel use of mocks with deep stubbing may lead to ConcurrentModificationException (#​2389)
• Add annotation to mark a type as DoNotMock (#​1833)
• Cannot mock this class: class java.io.InputStream with Java 13 (#​1827)
• Cannot mock wrapper types, String.class or Class.class (#​1734)

v4.0.0

Mockito 4: Removing deprecated APIs.

All of these APIs have been marked as deprecated and have been present
in Mockito for quite a while.

An overview of now-deleted classes/methods:

• org.mockito.Matchers which was an alias for
  org.mockito.ArgumentMatchers
• org.mockito.ArgumentMatchers#{anyObject,anyVararg} both which were
  aliases for org.mockito.ArgumentMatchers#any
• org.mockito.ArgumentMatchers#any*Of, which were aliases for the same
  method name without the Of and the generic parameters (which were
  ignored)
• org.mockito.ArgumentMatchers#{is}{Not}Null(Class) which took a class
  which was ignored. Aliases for the same methods without the parameter
• org.mockito.MockedStatic#verify which had the parameter types reversed
• org.mockito.Mockito#verifyZeroInteractions an alias of
  verifyNoMoreInteractions
• org.mockito.Mockito#debug framework integration API that we later
  refactored
• org.mockito.configuration.AnnotationEngine which was leaking internal
  APIs and instead users should use org.mockito.plugins.AnnotationEngine
• org.mockito.exceptions.verification.TooLittleActualInvocations fixed
  the grammar from "Little" to "Few"
• Numerous internal APIs that we never officially supported and can now
  remove
• org.mockito.plugins.InstantiatorProvider which was leaking internal
  APIs and instead users should use InstantiatorProvider2 (we should
  probably rename back to remove the number in a future major release)
• org.mockito.runners a package that hosted several old JUnit runners
  which were no longer supported. Users should instead use
  org.mockito.junit.MockitoJUnitRunner which is our official JUnit4
  runner.

---

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), 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 has been generated by Renovate Bot.