Update all dependencies

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	Age	Adoption	Passing	Confidence
actions/checkout	action	major	v1 -> v4
actions/setup-java	action	major	v1 -> v4
gradle (source)		minor	8.9 -> 8.10.2
androidx.test.espresso:espresso-core	dependencies	minor	3.5.1 -> 3.6.1
androidx.test.ext:junit	dependencies	minor	1.1.5 -> 1.2.1
com.google.android.gms:play-services-maps	dependencies	major	18.0.2 -> 19.0.0
com.google.android.gms:play-services-location	dependencies	major	16.0.0 -> 21.3.0
com.google.maps.android:android-maps-utils	dependencies	major	2.3.0 -> 3.8.2
androidx.compose.material3:material3-android (source)	dependencies	minor	1.2.1 -> 1.3.0
io.github.pushpalroy:jetlime	dependencies	major	2.0.1 -> 3.0.1
androidx.activity:activity-compose (source)	dependencies	minor	1.7.2 -> 1.9.2
com.google.firebase:firebase-bom	dependencies	major	26.2.0 -> 33.4.0
com.android.tools:desugar_jdk_libs	dependencies	minor	2.0.3 -> 2.1.2
org.mockito:mockito-inline	dependencies	major	3.11.2 -> 5.2.0
org.jetbrains.compose	plugin	minor	1.6.11 -> 1.7.0+build1877-release-1.7
com.google.maps.android:maps-compose-utils	dependencies	major	5.0.3 -> 6.1.2
com.google.maps.android:maps-compose	dependencies	major	5.0.3 -> 6.1.2
de.javagl:obj (source)	dependencies	minor	0.2.1 -> 0.4.0
io.github.qdsfdhvh:image-loader	dependencies	patch	1.8.3 -> 1.8.4
com.google.ar:core	dependencies	minor	1.4.0 -> 1.46.0
com.rickclephas.kmp.nativecoroutines	plugin	patch	1.0.0-ALPHA-35 -> 1.0.0-ALPHA-36

---

Release Notes

actions/checkout (actions/checkout)

v4

Compare Source

• Bump the minor-npm-dependencies group across 1 directory with 4 updates by @​dependabot in https://github.com/actions/checkout/pull/1739
• Bump actions/checkout from 3 to 4 by @​dependabot in https://github.com/actions/checkout/pull/1697
• Check out other refs/* by commit by @​orhantoy in https://github.com/actions/checkout/pull/1774
• Pin actions/checkout's own workflows to a known, good, stable version. by @​jww3 in https://github.com/actions/checkout/pull/1776

v3

Compare Source

• Fix: Mark test scripts with Bash'isms to be run via Bash
• Add option to fetch tags even if fetch-depth > 0

v2

Compare Source

• Fix default branch resolution for .wiki and when using SSH

actions/setup-java (actions/setup-java)

v4

Compare Source

v3

Compare Source

v2

Compare Source

gradle/gradle (gradle)

v8.10.2

Compare Source

v8.10.1

Compare Source

v8.10

Compare Source

googlemaps/android-maps-utils (com.google.maps.android:android-maps-utils)

v3.8.2

Bug Fixes

• IllegalArgumentException is clearer than ArrayIndexOutOfBounds (#​1241) (9c882be)

v3.8.1

Bug Fixes

• Correctly parse <hotSpot> elements (#​1173) (643d351)

v3.8.0

Features

• added street view source parameter to fetchStreetViewData (#​1262) (2fd3921)

v3.7.0

Features

• add support for Advanced Markers (#​1243) (c4cd47c), closes #​1242
• Upgrading the Maps SDK for Android dependency to v18.2.0 switches to the upgraded renderer as default renderer. See release notes at https://developers.google.com/maps/documentation/android-sdk/release-notes#October\_18\_2023

The upgraded renderer is required for Advanced Markers.

v3.6.1

Bug Fixes

• add dokka and fix doc generation (#​1249) (de47276)

v3.6.0

Features

• add additional response values to StreetViewUtil (#​1235) (46a07e3)

v3.5.3

Bug Fixes

• null check in onAnimationUpdate (#​1161) (3a5e35e)

v3.5.2

Bug Fixes

• bump gradle/wrapper-validation-action from 1.0.4 to 1.1.0 (#​1206) (933476a), closes #​1214

v3.5.1

Bug Fixes

• Add container ground overlays in KML/KMZ (#​1166) (2010bb7)

v3.5.0

Features

• added StreetViewUtil (#​1200) (83f961d)

v3.4.0

Features

• Add marker animation util (#​1151) (45b0cb5)

v3.3.0

Features

• Add function to set text appearance for cluster (#​1150) (72a880c)

v3.2.0

BREAKING CHANGES

• Add z-index to cluster markers (#​1136) (2a74367)

Apologies for breaking semantic versioning; only realized after release that the commit was not marked for breaking change.

v3.1.1

Bug Fixes

• fix the javadoc task and errors (#​1148) (2f0320f)

v3.1.0

Features

• exposing getColor function in the ClusterRenderer (#​1130) (0f0f9bd)

v3.0.0

Bug Fixes

• trigger major version release (15b90fe)

BREAKING CHANGES

• From #​1137 merged as commit 4038b7a, removed v3 library

v2.4.1

Bug Fixes

• Apply correction to distanceToLine() measurements (#​767) (59a48d3), closes /github.com/googlemaps/android-maps-utils/issues/720#issuecomment-631263199

v2.4.0

Features

• Allow changes to animation duration for marker splitting/merging effects (#​1098) (1930f6a)

pushpalroy/jetlime (io.github.pushpalroy:jetlime)

v3.0.1

Compare Source

• Fix: add dashed line effect/ pathEffect support for JetLimeExtendedEvent
• Add support for JS
• Update JVM to 17

What's Changed

• Optimize CI/CD workflow by @​pushpalroy in https://github.com/pushpalroy/JetLime/pull/41
• Add dashed line support for extended events by @​pushpalroy in https://github.com/pushpalroy/JetLime/pull/43

Full Changelog: pushpalroy/JetLime@3.0.0...3.0.1

v3.0.0

Compare Source

What's Changed

Migrated to Kotlin Multiplatform! 🚀 The library can now be used in Android, iOS, desktop, and Kotlin/wasm applications.

Contributors

• @​pisoj made their first contribution in https://github.com/pushpalroy/JetLime/pull/35

Full Changelog: pushpalroy/JetLime@2.3.0...3.0.0

v2.3.0

Compare Source

What's Changed

• Add pathEffect property to JetLimeStyle by @​keta1 in https://github.com/pushpalroy/JetLime/pull/37
• Add support for dashed timeline by @​pushpalroy in https://github.com/pushpalroy/JetLime/pull/38
• Release 2.3.0 by @​pushpalroy in https://github.com/pushpalroy/JetLime/pull/40
• Bump Kotlin to 1.9.25
• Bump Compose compiler to 1.5.15

New Contributors

• @​keta1 made their first contribution in https://github.com/pushpalroy/JetLime/pull/37

Full Changelog: pushpalroy/JetLime@2.2.1...2.3.0

v2.2.1

Compare Source

1. Bump AGP to 8.4.2
2. Bump composeBom to 2024.06.00
3. Bump kotlin to 1.9.24
4. Bump activityCompose to 1.9.1
5. Bump coreKtx to 1.13.1
6. Bump lifecycleRuntimeKtx to 2.8.4

What's Changed

• Release 2.2.1 by @​pushpalroy in https://github.com/pushpalroy/JetLime/pull/36

Full Changelog: pushpalroy/JetLime@2.2.0...2.2.1

v2.2.0

Compare Source

• Add support for custom icon tint for custom pointType
• The pointColor will now be used as the background for the custom icon
• Fix the issue with custom icon animation
• Bump compose BOM to 2024.03.00
• Bump AGP to 8.3.1
• Update samples

What's Changed

• Add support for custom icon tint and background by @​pushpalroy in https://github.com/pushpalroy/JetLime/pull/32

Full Changelog: pushpalroy/JetLime@2.1.1...2.2.0

v2.1.1

Compare Source

• Migrate to Compose BOM 2024.02.01
• Bump Gradle to 8.4
• Improve samples performance

Full Changelog: pushpalroy/JetLime@2.1.0...2.1.1

v2.1.0

Compare Source

New API added

A new composable API JetLimeExtendedEvent has been added.

Features of this composable:

• Create a JetLimeColumn event that has 2 slots for content.
• The main content will be drawn on the right side of the timeline and the additional content will be drawn on the left side of the timeline.
• The additional content is optional and has a maximum width, which can be configured.

What's Changed

• Add API JetLimeExtendedEvent composable by @​pushpalroy in https://github.com/pushpalroy/jetlime/pull/23

Full Changelog: pushpalroy/JetLime@2.0.1...2.1.0

google/desugar_jdk_libs (com.android.tools:desugar_jdk_libs)

v2.1.2

• Added support for standalone weekday names. Before they were returned as
  numbers 1 through 7.
  See issue 362277530

v2.1.1

• Fixed issue with incorrect standalone month name.
  See issue 355577226

v2.1.0

• Support default method java.util.Collection#toArray(java.util.function.IntFunction).
• Improve collection wrapping through java.util.Collections.
  See c01a5446ca13586b801dbba4d83c6821337b3cc2 for implementation details.
• Requires AGP version 8.0.0 or later (Android Studio 2022.2.1 stable).

v2.0.4

• Better support for "stand-alone" month names ("LLLL" format).
  See (issue 160113376)
  for details.
• Added support for java.util.Base64 introduced in API level 26
• Workaround for some non ASCII characters
  (issue 293388944)

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

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 [(#&#

---

Configuration

📅 Schedule: Branch creation - "before 4am" (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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.