build(deps): bump the maven-dependencies group with 13 updates #534

dependabot · 2024-10-06T15:08:17Z

Bumps the maven-dependencies group with 13 updates:

Package	From	To
org.mockito:mockito-core	`4.11.0`	`5.0.0`
org.mockito:mockito-junit-jupiter	`4.11.0`	`5.0.0`
org.springframework.boot:spring-boot-configuration-processor	`2.7.18`	`3.0.0`
org.springframework.boot:spring-boot-starter	`2.7.18`	`3.0.0`
org.springframework.boot:spring-boot-starter-test	`2.7.18`	`3.0.0`
org.springframework.boot:spring-boot-starter-web	`2.7.18`	`3.0.0`
org.springframework.boot:spring-boot-starter-validation	`2.7.18`	`3.0.0`
org.springframework.boot:spring-boot-maven-plugin	`2.7.18`	`3.0.0`
org.apache.maven.plugins:maven-failsafe-plugin	`3.5.0`	`3.5.1`
org.apache.maven.plugins:maven-javadoc-plugin	`3.10.0`	`3.10.1`
org.testcontainers:junit-jupiter	`1.20.1`	`1.20.2`
org.testcontainers:kafka	`1.20.1`	`1.20.2`
org.testcontainers:testcontainers-bom	`1.20.1`	`1.20.2`

Updates org.mockito:mockito-core from 4.11.0 to 5.0.0

Release notes

Sourced from org.mockito:mockito-core's releases.

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.

... (truncated)

Commits

adf528d Bump versions.bytebuddy from 1.12.21 to 1.12.22 (#2864)
2418419 Bump versions.junitJupiter from 5.9.1 to 5.9.2 (#2858)
3d40cd5 Bump junit-platform-launcher from 1.9.1 to 1.9.2 (#2859)
9bec8e3 Bump versions.errorprone from 2.17.0 to 2.18.0 (#2857)
a9595f5 Switch the default mockmaker to the inline mockmaker on JDK 17+ (#2834)
c5d7fbc Bump assertj-core from 3.23.1 to 3.24.1 (#2854)
dbd7f2f Bump versions.bytebuddy from 1.12.20 to 1.12.21 (#2852)
4d62fa7 Bump junit from 1.1.4 to 1.1.5 (#2850)
b1b6d6a Bump espresso-core from 3.5.0 to 3.5.1 (#2849)
7b5b8dd Remove use case for non-existent method VerificationWithTimeout#never (#2848)
Additional commits viewable in compare view

Updates org.mockito:mockito-junit-jupiter from 4.11.0 to 5.0.0

Release notes

Sourced from org.mockito:mockito-junit-jupiter's releases.

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.

... (truncated)

Commits

adf528d Bump versions.bytebuddy from 1.12.21 to 1.12.22 (#2864)
2418419 Bump versions.junitJupiter from 5.9.1 to 5.9.2 (#2858)
3d40cd5 Bump junit-platform-launcher from 1.9.1 to 1.9.2 (#2859)
9bec8e3 Bump versions.errorprone from 2.17.0 to 2.18.0 (#2857)
a9595f5 Switch the default mockmaker to the inline mockmaker on JDK 17+ (#2834)
c5d7fbc Bump assertj-core from 3.23.1 to 3.24.1 (#2854)
dbd7f2f Bump versions.bytebuddy from 1.12.20 to 1.12.21 (#2852)
4d62fa7 Bump junit from 1.1.4 to 1.1.5 (#2850)
b1b6d6a Bump espresso-core from 3.5.0 to 3.5.1 (#2849)
7b5b8dd Remove use case for non-existent method VerificationWithTimeout#never (#2848)
Additional commits viewable in compare view

Updates org.mockito:mockito-junit-jupiter from 4.11.0 to 5.0.0

Release notes

Sourced from org.mockito:mockito-junit-jupiter's releases.

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.

... (truncated)

Commits

adf528d Bump versions.bytebuddy from 1.12.21 to 1.12.22 (#2864)
2418419 Bump versions.junitJupiter from 5.9.1 to 5.9.2 (#2858)
3d40cd5 Bump junit-platform-launcher from 1.9.1 to 1.9.2 (#2859)
9bec8e3 Bump versions.errorprone from 2.17.0 to 2.18.0 (#2857)
a9595f5 Switch the default mockmaker to the inline mockmaker on JDK 17+ (#2834)
c5d7fbc Bump assertj-core from 3.23.1 to 3.24.1 (#2854)
dbd7f2f Bump versions.bytebuddy from 1.12.20 to 1.12.21 (#2852)
4d62fa7 Bump junit from 1.1.4 to 1.1.5 (#2850)
b1b6d6a Bump espresso-core from 3.5.0 to 3.5.1 (#2849)
7b5b8dd Remove use case for non-existent method VerificationWithTimeout#never (#2848)
Additional commits viewable in compare view

Updates org.springframework.boot:spring-boot-configuration-processor from 2.7.18 to 3.0.0

Release notes

Sourced from org.springframework.boot:spring-boot-configuration-processor's releases.

v3.0.0

See the Release notes for 3.0 for upgrade instructions and details of new features.

⭐ New Features

Provide a configuration property for the observation patterns of Spring Integration components #33099

🐞 Bug Fixes

io.micrometer.tracing.Tracer on the classpath breaks AOT processing for tests #33298

Tracer library HTTP instrumentation is auto-configured unnecessarily #33287

Auto-configuration ignores user-provided ObservationConventions #33285

ScheduledBeanLazyInitializationExcludeFilter is auto-configured even when annotation-based scheduled has not been enabled #33284

SpringBootContextLoader prints banner twice when using a @ContextHierarchy #33263

Properties migrator causes an application to fail to start if it tries to map a property whose metadata data entry contains an invalid configuration property name #33250

Wavefront MeterRegistryCustomizer is not applying application tags from application.properties #33244

Actuator responses no longer format timestamps as ISO-8601 #33236

Configuration property is not bound in a native image when property has get, set, and is methods #33232

Configuration property binding does not deal with bridge methods #33212

Contribute missing resource hints for GraphQL schema files and GraphiQL HTML page #33208

Hints for ClientHttpRequestFactory should only be generated for matching methods #33203

Native profile should configure execution in pluginManagement #33184

Configuring management.server.port via a config tree results in a ConverterNotFoundException when the management context is refreshed #33169

JBoss logging does not route directly to SLF4J when using Logback #33155

Test with UseMainMethod.Always do not work with Kotlin main functions #33114

Maven process-aot does not specify source and target release when compiling generated sources #33112

Some Actuator beans are ineligible for post-processing #33110

AOT-generated source fails to compile when Actuator is enabled on a WebFlux project #33106

@ContextHierarchy should never be used with main method #33078

Maven process-aot fails when compiler plugin has been configured with --enable-preview #33012

Wavefront application tags differ from those used in a Spring Boot 2.x application #32844

Maven goal spring-boot:build-image runs package phase twice #26455

📔 Documentation

Document observation for R2DBC #33335

Align Tomcat multiple connectors example with recommendation to configure SSL declaratively #33333

Actuator document is misleading about k8s startup probe #33327

Update documented for @Timed to reflect narrower support #33282

Update reference documentation to replace mentions of tags providers and contributors with their Observation-based equivalents #33281

Link to Micrometer's @Timed documentation #33266

Clarify use of the spring.cache.type property with Hazelcast #33258

Example git.commit.time in the Actuator API documentation is thousands of years in the future #33256

Update Spring Security filter dispatcher types docs to reflect change in default value #33252

Documentation for nested configuration properties in a native image uses @NestedConfigurationProperty too widely #33239

Document that the jar task should not be disabled when building a native image #33238

Document nesting configuration properties using records or Kotlin data classes and how and when to use @NestedConfigurationProperty #33235

Links to Features describes sections that have moved elsewhere #33214

Fix broken links in docs #33209

Document the need for compilation with -parameters when targeting a native image #33182

... (truncated)

Commits

c9c359f Release v3.0.0
fb2cc73 Work around Thymeleaf's dependency on spring-security-bom:6.0.0-RC2
355b428 Merge branch '2.7.x'
7ea5881 Update LATEST_GA to false to prepare for 3.0.0's release
1de09f4 Merge branch '2.6.x' into 2.7.x
e922650 Upgrade to Spring Framework 6.0.2
4b8a28a Next development version (v2.7.7-SNAPSHOT)
14ba9b1 Start building against Spring Framework 6.0.2 snapshots
d4a9100 Next development version (v2.6.15-SNAPSHOT)
28cb225 Merge branch '2.7.x'
Additional commits viewable in compare view

Updates org.springframework.boot:spring-boot-starter from 2.7.18 to 3.0.0

Release notes

Sourced from org.springframework.boot:spring-boot-starter's releases.

v3.0.0

See the Release notes for 3.0 for upgrade instructions and details of new features.

⭐ New Features

Provide a configuration property for the observation patterns of Spring Integration components #33099

🐞 Bug Fixes

io.micrometer.tracing.Tracer on the classpath breaks AOT processing for tests #33298

Tracer library HTTP instrumentation is auto-configured unnecessarily #33287

Auto-configuration ignores user-provided ObservationConventions #33285

ScheduledBeanLazyInitializationExcludeFilter is auto-configured even when annotation-based scheduled has not been enabled #33284

SpringBootContextLoader prints banner twice when using a @ContextHierarchy #33263

Properties migrator causes an application to fail to start if it tries to map a property whose metadata data entry contains an invalid configuration property name #33250

Wavefront MeterRegistryCustomizer is not applying application tags from application.properties #33244

Actuator responses no longer format timestamps as ISO-8601 #33236

Configuration property is not bound in a native image when property has get, set, and is methods #33232

Configuration property binding does not deal with bridge methods #33212

Contribute missing resource hints for GraphQL schema files and GraphiQL HTML page #33208

Hints for ClientHttpRequestFactory should only be generated for matching methods #33203

Native profile should configure execution in pluginManagement #33184

Configuring management.server.port via a config tree results in a ConverterNotFoundException when the management context is refreshed #33169

JBoss logging does not route directly to SLF4J when using Logback #33155

Test with UseMainMethod.Always do not work with Kotlin main functions #33114

Maven process-aot does not specify source and target release when compiling generated sources #33112

Some Actuator beans are ineligible for post-processing #33110

AOT-generated source fails to compile when Actuator is enabled on a WebFlux project #33106

@ContextHierarchy should never be used with main method #33078

Maven process-aot fails when compiler plugin has been configured with --enable-preview #33012

Wavefront application tags differ from those used in a Spring Boot 2.x application #32844

Maven goal spring-boot:build-image runs package phase twice #26455

📔 Documentation

Document observation for R2DBC #33335

Align Tomcat multiple connectors example with recommendation to configure SSL declaratively #33333

Actuator document is misleading about k8s startup probe #33327

Update documented for @Timed to reflect narrower support #33282

Update reference documentation to replace mentions of tags providers and contributors with their Observation-based equivalents #33281

Link to Micrometer's @Timed documentation #33266

Clarify use of the spring.cache.type property with Hazelcast #33258

Example git.commit.time in the Actuator API documentation is thousands of years in the future #33256

Update Spring Security filter dispatcher types docs to reflect change in default value #33252

Documentation for nested configuration properties in a native image uses @NestedConfigurationProperty too widely #33239

Document that the jar task should not be disabled when building a native image #33238

Document nesting configuration properties using records or Kotlin data classes and how and when to use @NestedConfigurationProperty #33235

Links to Features describes sections that have moved elsewhere #33214

Fix broken links in docs #33209

Document the need for compilation with -parameters when targeting a native image #33182

... (truncated)

Commits

c9c359f Release v3.0.0
fb2cc73 Work around Thymeleaf's dependency on spring-security-bom:6.0.0-RC2
355b428 Merge branch '2.7.x'
7ea5881 Update LATEST_GA to false to prepare for 3.0.0's release
1de09f4 Merge branch '2.6.x' into 2.7.x
e922650 Upgrade to Spring Framework 6.0.2
4b8a28a Next development version (v2.7.7-SNAPSHOT)
14ba9b1 Start building against Spring Framework 6.0.2 snapshots
d4a9100 Next development version (v2.6.15-SNAPSHOT)
28cb225 Merge branch '2.7.x'
Additional commits viewable in compare view

Updates org.springframework.boot:spring-boot-starter-test from 2.7.18 to 3.0.0

Release notes

Sourced from org.springframework.boot:spring-boot-starter-test's releases.

v3.0.0

See the Release notes for 3.0 for upgrade instructions and details of new features.

⭐ New Features

Provide a configuration property for the observation patterns of Spring Integration components #33099

🐞 Bug Fixes

io.micrometer.tracing.Tracer on the classpath breaks AOT processing for tests #33298

Tracer library HTTP instrumentation is auto-configured unnecessarily #33287

Auto-configuration ignores user-provided ObservationConventions #33285

ScheduledBeanLazyInitializationExcludeFilter is auto-configured even when annotation-based scheduled has not been enabled #33284

SpringBootContextLoader prints banner twice when using a @ContextHierarchy #33263

Properties migrator causes an application to fail to start if it tries to map a property whose metadata data entry contains an invalid configuration property name #33250

Wavefront MeterRegistryCustomizer is not applying application tags from application.properties #33244

Actuator responses no longer format timestamps as ISO-8601 #33236

Configuration property is not bound in a native image when property has get, set, and is methods #33232

Configuration property binding does not deal with bridge methods #33212

Contribute missing resource hints for GraphQL schema files and GraphiQL HTML page #33208

Hints for ClientHttpRequestFactory should only be generated for matching methods #33203

Native profile should configure execution in pluginManagement #33184

Configuring management.server.port via a config tree results in a ConverterNotFoundException when the management context is refreshed #33169

JBoss logging does not route directly to SLF4J when using Logback #33155

Test with UseMainMethod.Always do not work with Kotlin main functions #33114

Maven process-aot does not specify source and target release when compiling generated sources #33112

Some Actuator beans are ineligible for post-processing #33110

AOT-generated source fails to compile when Actuator is enabled on a WebFlux project #33106

@ContextHierarchy should never be used with main method #33078

Maven process-aot fails when compiler plugin has been configured with --enable-preview #33012

Wavefront application tags differ from those used in a Spring Boot 2.x application #32844

Maven goal spring-boot:build-image runs package phase twice #26455

📔 Documentation

Document observation for R2DBC #33335

Align Tomcat multiple connectors example with recommendation to configure SSL declaratively #33333

Actuator document is misleading about k8s startup probe #33327

Update documented for @Timed to reflect narrower support #33282

Update reference documentation to replace mentions of tags providers and contributors with their Observation-based equivalents #33281

Link to Micrometer's @Timed documentation #33266

Clarify use of the spring.cache.type property with Hazelcast #33258

Example git.commit.time in the Actuator API documentation is thousands of years in the future #33256

Update Spring Security filter dispatcher types docs to reflect change in default value #33252

Documentation for nested configuration properties in a native image uses @NestedConfigurationProperty too widely #33239

Document that the jar task should not be disabled when building a native image #33238

Document nesting configuration properties using records or Kotlin data classes and how and when to use @NestedConfigurationProperty #33235

Links to Features describes sections that have moved elsewhere #33214

Fix broken links in docs #33209

Document the need for compilation with -parameters when targeting a native image #33182

... (truncated)

Commits

c9c359f Release v3.0.0
fb2cc73 Work around Thymeleaf's dependency on spring-security-bom:6.0.0-RC2
355b428 Merge branch '2.7.x'
7ea5881 Update LATEST_GA to false to prepare for 3.0.0's release
1de09f4 Merge branch '2.6.x' into 2.7.x
e922650 Upgrade to Spring Framework 6.0.2
4b8a28a Next development version (v2.7.7-SNAPSHOT)
14ba9b1 Start building against Spring Framework 6.0.2 snapshots
d4a9100 Next development version (v2.6.15-SNAPSHOT)
28cb225 Merge branch '2.7.x'
Additional commits viewable in compare view

Updates org.springframework.boot:spring-boot-starter-web from 2.7.18 to 3.0.0

Release notes

Sourced from org.springframework.boot:spring-boot-starter-web's releases.

v3.0.0

See the Release notes for 3.0 for upgrade instructions and details of new features.

⭐ New Features

Provide a configuration property for the observation patterns of Spring Integration components #33099

🐞 Bug Fixes

io.micrometer.tracing.Tracer on the classpath breaks AOT processing for tests #33298

Tracer library HTTP instrumentation is auto-configured unnecessarily #33287

Auto-configuration ignores user-provided ObservationConventions #33285

ScheduledBeanLazyInitializationExcludeFilter is auto-configured even when annotation-based scheduled has not been enabled #33284

SpringBootContextLoader prints banner twice when using a @ContextHierarchy #33263

Properties migrator causes an application to fail to start if it tries to map a property whose metadata data entry contains an invalid configuration property name #33250

Wavefront MeterRegistryCustomizer is not applying application tags from application.properties #33244

Actuator responses no longer format timestamps as ISO-8601 #33236

Configuration property is not bound in a native image when property has get, set, and is methods #33232

Configuration property binding does not deal with bridge methods #33212

Contribute missing resource hints for GraphQL schema files and GraphiQL HTML page #33208

Hints for ClientHttpRequestFactory should only be generated for matching methods #33203

Native profile should configure execution in pluginManagement #33184

Configuring management.server.port via a config tree results in a ConverterNotFoundException when the management context is refreshed #33169

JBoss logging does not route directly to SLF4J when using Logback #33155

Test with UseMainMethod.Always do not work with Kotlin main functions #33114

Maven process-aot does not specify source and target release when compiling generated sources #33112

Some Actuator beans are ineligible for post-processing #33110

AOT-generated source fails to compile when Actuator is enabled on a WebFlux project #33106

@ContextHierarchy should never be used with main method #33078

Maven process-aot fails when compiler plugin has been configured with --enable-preview #33012

Wavefront application tags differ from those used in a Spring Boot 2.x application #32844

Maven goal spring-boot:build-image runs package phase twice #26455

📔 Documentation

Document observation for R2DBC #33335

Align Tomcat multiple connectors example with recommendation to configure SSL declaratively #33333

Actuator document is misleading about k8s startup probe #33327

Update documented for @Timed to reflect narrower support #33282

Update reference documentation to replace mentions of tags providers and contributors with their Observation-based equivalents #33281

Link to Micrometer's @Timed documentation #33266

Clarify use of the spring.cache.type property with Hazelcast #33258

Example git.commit.time in the Actuator API documentation is thousands of years in the future #33256

Update Spring Security filter dispatcher types docs to reflect change in default value #33252

Documentation for nested configuration properties in a native image uses @NestedConfigurationProperty too widely #33239

Document that the jar task should not be disabled when building a native image #33238

Document nesting configuration properties using records or Kotlin data classes and how and when to use @NestedConfigurationProperty #33235

Links to Features describes sections that have moved elsewhere #33214

Fix broken links in docs #33209

Document the need for compilation with -parameters when targeting a native image #33182

... (truncated)

Commits

c9c359f Release v3.0.0
fb2cc73 Work around Thymeleaf's dependency on spring-security-bom:6.0.0-RC2
355b428 Merge branch '2.7.x'
7ea5881 Update LATEST_GA to false to prepare for 3.0.0's release
1de09f4 Merge branch '2.6.x' into 2.7.x
e922650 Upgrade to Spring Framework 6.0.2
4b8a28a Next development version (v2.7.7-SNAPSHOT)
14ba9b1 Start building against Spring Framework 6.0.2 snapshots
d4a9100 Next development version (v2.6.15-SNAPSHOT)
28cb225 Merge branch '2.7.x'
Additional commits viewable in compare view

Updates org.springframework.boot:spring-boot-starter-validation from 2.7.18 to 3.0.0

Release notes

Sourced from org.springframework.boot:spring-boot-starter-validation's releases.

v3.0.0

See the Release notes for 3.0 for upgrade instructions and details of new features.

⭐ New Features

Provide a configuration property for the observation patterns of Spring Integration components #33099

🐞 Bug Fixes

io.micrometer.tracing.Tracer on the classpath breaks AOT processing for tests #33298

Tracer library HTTP instrumentation is auto-configured unnecessarily #33287

Auto-configuration ignores user-provided ObservationConventions #33285

ScheduledBeanLazyInitializationExcludeFilter is auto-configured even when annotation-based scheduled has not been enabled #33284

SpringBootContextLoader prints banner twice when using a @ContextHierarchy #33263

Properties migrator causes an application to fail to start if it tries to map a property whose metadata data entry contains an invalid configuration property name #33250

Wavefront MeterRegistryCustomizer is not applying application tags from application.properties #33244

Actuator responses no longer format timestamps as ISO-8601 #33236

Configuration property is not bound in a native image when property has get, set, and is methods #33232

Configuration property binding does not deal with bridge methods #33212

Contribute missing resource hints for GraphQL schema files and GraphiQL HTML page #33208

Hints for ClientHttpRequestFactory should only be generated for matching methods #33203

Native profile should configure execution in pluginManagement #33184

Configuring management.server.port via a config tree results in a ConverterNotFoundException when the management context is refreshed #33169

JBoss logging does not route directly to SLF4J when using Logback #33155

Test with UseMainMethod.Always do not work with Kotlin main ...
Description has been truncated

Bumps the maven-dependencies group with 13 updates: | Package | From | To | | --- | --- | --- | | [org.mockito:mockito-core](https://github.com/mockito/mockito) | `4.11.0` | `5.0.0` | | [org.mockito:mockito-junit-jupiter](https://github.com/mockito/mockito) | `4.11.0` | `5.0.0` | | [org.springframework.boot:spring-boot-configuration-processor](https://github.com/spring-projects/spring-boot) | `2.7.18` | `3.0.0` | | [org.springframework.boot:spring-boot-starter](https://github.com/spring-projects/spring-boot) | `2.7.18` | `3.0.0` | | [org.springframework.boot:spring-boot-starter-test](https://github.com/spring-projects/spring-boot) | `2.7.18` | `3.0.0` | | [org.springframework.boot:spring-boot-starter-web](https://github.com/spring-projects/spring-boot) | `2.7.18` | `3.0.0` | | [org.springframework.boot:spring-boot-starter-validation](https://github.com/spring-projects/spring-boot) | `2.7.18` | `3.0.0` | | [org.springframework.boot:spring-boot-maven-plugin](https://github.com/spring-projects/spring-boot) | `2.7.18` | `3.0.0` | | [org.apache.maven.plugins:maven-failsafe-plugin](https://github.com/apache/maven-surefire) | `3.5.0` | `3.5.1` | | [org.apache.maven.plugins:maven-javadoc-plugin](https://github.com/apache/maven-javadoc-plugin) | `3.10.0` | `3.10.1` | | [org.testcontainers:junit-jupiter](https://github.com/testcontainers/testcontainers-java) | `1.20.1` | `1.20.2` | | [org.testcontainers:kafka](https://github.com/testcontainers/testcontainers-java) | `1.20.1` | `1.20.2` | | [org.testcontainers:testcontainers-bom](https://github.com/testcontainers/testcontainers-java) | `1.20.1` | `1.20.2` | Updates `org.mockito:mockito-core` from 4.11.0 to 5.0.0 - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.11.0...v5.0.0) Updates `org.mockito:mockito-junit-jupiter` from 4.11.0 to 5.0.0 - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.11.0...v5.0.0) Updates `org.mockito:mockito-junit-jupiter` from 4.11.0 to 5.0.0 - [Release notes](https://github.com/mockito/mockito/releases) - [Commits](mockito/mockito@v4.11.0...v5.0.0) Updates `org.springframework.boot:spring-boot-configuration-processor` from 2.7.18 to 3.0.0 - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.18...v3.0.0) Updates `org.springframework.boot:spring-boot-starter` from 2.7.18 to 3.0.0 - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.18...v3.0.0) Updates `org.springframework.boot:spring-boot-starter-test` from 2.7.18 to 3.0.0 - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.18...v3.0.0) Updates `org.springframework.boot:spring-boot-starter-web` from 2.7.18 to 3.0.0 - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.18...v3.0.0) Updates `org.springframework.boot:spring-boot-starter-validation` from 2.7.18 to 3.0.0 - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.18...v3.0.0) Updates `org.springframework.boot:spring-boot-maven-plugin` from 2.7.18 to 3.0.0 - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.18...v3.0.0) Updates `org.springframework.boot:spring-boot-starter` from 2.7.18 to 3.0.0 - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.18...v3.0.0) Updates `org.apache.maven.plugins:maven-failsafe-plugin` from 3.5.0 to 3.5.1 - [Release notes](https://github.com/apache/maven-surefire/releases) - [Commits](apache/maven-surefire@surefire-3.5.0...surefire-3.5.1) Updates `org.apache.maven.plugins:maven-javadoc-plugin` from 3.10.0 to 3.10.1 - [Release notes](https://github.com/apache/maven-javadoc-plugin/releases) - [Commits](apache/maven-javadoc-plugin@maven-javadoc-plugin-3.10.0...maven-javadoc-plugin-3.10.1) Updates `org.testcontainers:junit-jupiter` from 1.20.1 to 1.20.2 - [Release notes](https://github.com/testcontainers/testcontainers-java/releases) - [Changelog](https://github.com/testcontainers/testcontainers-java/blob/main/CHANGELOG.md) - [Commits](testcontainers/testcontainers-java@1.20.1...1.20.2) Updates `org.testcontainers:kafka` from 1.20.1 to 1.20.2 - [Release notes](https://github.com/testcontainers/testcontainers-java/releases) - [Changelog](https://github.com/testcontainers/testcontainers-java/blob/main/CHANGELOG.md) - [Commits](testcontainers/testcontainers-java@1.20.1...1.20.2) Updates `org.testcontainers:kafka` from 1.20.1 to 1.20.2 - [Release notes](https://github.com/testcontainers/testcontainers-java/releases) - [Changelog](https://github.com/testcontainers/testcontainers-java/blob/main/CHANGELOG.md) - [Commits](testcontainers/testcontainers-java@1.20.1...1.20.2) Updates `org.springframework.boot:spring-boot-starter-test` from 2.7.18 to 3.0.0 - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.18...v3.0.0) Updates `org.springframework.boot:spring-boot-starter-web` from 2.7.18 to 3.0.0 - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.18...v3.0.0) Updates `org.springframework.boot:spring-boot-starter-validation` from 2.7.18 to 3.0.0 - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.18...v3.0.0) Updates `org.springframework.boot:spring-boot-maven-plugin` from 2.7.18 to 3.0.0 - [Release notes](https://github.com/spring-projects/spring-boot/releases) - [Commits](spring-projects/spring-boot@v2.7.18...v3.0.0) Updates `org.testcontainers:testcontainers-bom` from 1.20.1 to 1.20.2 - [Release notes](https://github.com/testcontainers/testcontainers-java/releases) - [Changelog](https://github.com/testcontainers/testcontainers-java/blob/main/CHANGELOG.md) - [Commits](testcontainers/testcontainers-java@1.20.1...1.20.2) --- updated-dependencies: - dependency-name: org.mockito:mockito-core dependency-type: direct:development update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.mockito:mockito-junit-jupiter dependency-type: direct:development update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.mockito:mockito-junit-jupiter dependency-type: direct:development update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.springframework.boot:spring-boot-configuration-processor dependency-type: direct:production update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.springframework.boot:spring-boot-starter dependency-type: direct:production update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.springframework.boot:spring-boot-starter-test dependency-type: direct:development update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.springframework.boot:spring-boot-starter-web dependency-type: direct:production update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.springframework.boot:spring-boot-starter-validation dependency-type: direct:production update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.springframework.boot:spring-boot-maven-plugin dependency-type: direct:production update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.springframework.boot:spring-boot-starter dependency-type: direct:production update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.apache.maven.plugins:maven-failsafe-plugin dependency-type: direct:production update-type: version-update:semver-patch dependency-group: maven-dependencies - dependency-name: org.apache.maven.plugins:maven-javadoc-plugin dependency-type: direct:production update-type: version-update:semver-patch dependency-group: maven-dependencies - dependency-name: org.testcontainers:junit-jupiter dependency-type: direct:production update-type: version-update:semver-patch dependency-group: maven-dependencies - dependency-name: org.testcontainers:kafka dependency-type: direct:development update-type: version-update:semver-patch dependency-group: maven-dependencies - dependency-name: org.testcontainers:kafka dependency-type: direct:development update-type: version-update:semver-patch dependency-group: maven-dependencies - dependency-name: org.springframework.boot:spring-boot-starter-test dependency-type: direct:development update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.springframework.boot:spring-boot-starter-web dependency-type: direct:production update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.springframework.boot:spring-boot-starter-validation dependency-type: direct:production update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.springframework.boot:spring-boot-maven-plugin dependency-type: direct:production update-type: version-update:semver-major dependency-group: maven-dependencies - dependency-name: org.testcontainers:testcontainers-bom dependency-type: direct:production update-type: version-update:semver-patch dependency-group: maven-dependencies ... Signed-off-by: dependabot[bot] <[email protected]>

smcvb · 2024-10-07T11:16:15Z

@dependabot ignore org.mockito:mockito-core minor version

smcvb · 2024-10-07T11:16:17Z

@dependabot ignore org.mockito:mockito-core major version

dependabot · 2024-10-07T11:16:18Z

OK, I won't notify you about version 5.0.x of org.mockito:mockito-core again, unless you unignore it.

smcvb · 2024-10-07T11:16:19Z

@dependabot show org.mockito:mockito-core ignore conditions

dependabot · 2024-10-07T11:16:20Z

OK, I won't notify you about version 5.x.x of org.mockito:mockito-core again, unless you unignore it.

dependabot · 2024-10-07T11:16:22Z

Ignore Conditions

Dependency	Ignore Condition
org.mockito:mockito-core	[>= 5.0.a, < 5.1]
org.mockito:mockito-core	[>= 5.a, < 6]

smcvb · 2024-10-07T11:16:28Z

@dependabot ignore org.mockito:mockito-junit-jupiter minor version

dependabot · 2024-10-07T11:16:30Z

OK, I won't notify you about version 5.0.x of org.mockito:mockito-junit-jupiter again, unless you unignore it.

smcvb · 2024-10-07T11:16:31Z

@dependabot ignore org.mockito:mockito-junit-jupiter major version

dependabot · 2024-10-07T11:16:34Z

OK, I won't notify you about version 5.x.x of org.mockito:mockito-junit-jupiter again, unless you unignore it.

smcvb · 2024-10-07T11:16:36Z

@dependabot show org.mockito:mockito-junit-jupiter ignore conditions

dependabot · 2024-10-07T11:16:39Z

Ignore Conditions

Dependency	Ignore Condition
org.mockito:mockito-junit-jupiter	[>= 5.0.a, < 5.1]
org.mockito:mockito-junit-jupiter	[>= 5.a, < 6]

smcvb · 2024-10-07T11:16:43Z

@dependabot ignore org.springframework.boot:spring-boot-configuration-processor minor version

dependabot · 2024-10-07T11:16:46Z

OK, I won't notify you about version 3.0.x of org.springframework.boot:spring-boot-configuration-processor again, unless you unignore it.

smcvb · 2024-10-07T11:16:46Z

@dependabot ignore org.springframework.boot:spring-boot-configuration-processor major version

dependabot · 2024-10-07T11:16:49Z

OK, I won't notify you about version 3.x.x of org.springframework.boot:spring-boot-configuration-processor again, unless you unignore it.

smcvb · 2024-10-07T11:16:49Z

@dependabot show org.springframework.boot:spring-boot-configuration-processor ignore conditions

dependabot · 2024-10-07T11:16:51Z

Ignore Conditions

Dependency	Ignore Condition
org.springframework.boot:spring-boot-configuration-processor	[>= 3.0.a, < 3.1]
org.springframework.boot:spring-boot-configuration-processor	[>= 3.a, < 4]

smcvb · 2024-10-07T11:16:57Z

@dependabot ignore org.springframework.boot:spring-boot-starter minor version

dependabot · 2024-10-07T11:16:59Z

OK, I won't notify you about version 3.0.x of org.springframework.boot:spring-boot-starter again, unless you unignore it.

smcvb · 2024-10-07T11:16:59Z

@dependabot ignore org.springframework.boot:spring-boot-starter major version

smcvb · 2024-10-07T11:17:25Z

@dependabot ignore org.springframework.boot:spring-boot-starter-web minor version

dependabot · 2024-10-07T11:17:27Z

OK, I won't notify you about version 3.0.x of org.springframework.boot:spring-boot-starter-web again, unless you unignore it.

smcvb · 2024-10-07T11:17:27Z

@dependabot ignore org.springframework.boot:spring-boot-starter-web major version

smcvb · 2024-10-07T11:17:30Z

@dependabot show org.springframework.boot:spring-boot-starter-web ignore conditions

dependabot · 2024-10-07T11:17:30Z

OK, I won't notify you about version 3.x.x of org.springframework.boot:spring-boot-starter-web again, unless you unignore it.

dependabot · 2024-10-07T11:17:32Z

Ignore Conditions

Dependency	Ignore Condition
org.springframework.boot:spring-boot-starter-web	[>= 3.0.a, < 3.1]
org.springframework.boot:spring-boot-starter-web	[>= 3.a, < 4]

smcvb · 2024-10-07T11:17:36Z

@dependabot ignore org.springframework.boot:spring-boot-starter-validation minor version

smcvb · 2024-10-07T11:17:38Z

@dependabot ignore org.springframework.boot:spring-boot-starter-validation major version

dependabot · 2024-10-07T11:17:38Z

OK, I won't notify you about version 3.0.x of org.springframework.boot:spring-boot-starter-validation again, unless you unignore it.

smcvb · 2024-10-07T11:17:40Z

@dependabot show org.springframework.boot:spring-boot-starter-validation ignore conditions

dependabot · 2024-10-07T11:17:41Z

OK, I won't notify you about version 3.x.x of org.springframework.boot:spring-boot-starter-validation again, unless you unignore it.

dependabot · 2024-10-07T11:17:43Z

Ignore Conditions

Dependency	Ignore Condition
org.springframework.boot:spring-boot-starter-validation	[>= 3.0.a, < 3.1]
org.springframework.boot:spring-boot-starter-validation	[>= 3.a, < 4]

smcvb · 2024-10-07T11:17:47Z

@dependabot ignore org.springframework.boot:spring-boot-maven-plugin minor version

smcvb · 2024-10-07T11:17:49Z

@dependabot ignore org.springframework.boot:spring-boot-maven-plugin major version

dependabot · 2024-10-07T11:17:51Z

OK, I won't notify you about version 3.0.x of org.springframework.boot:spring-boot-maven-plugin again, unless you unignore it.

dependabot · 2024-10-07T11:17:52Z

OK, I won't notify you about version 3.x.x of org.springframework.boot:spring-boot-maven-plugin again, unless you unignore it.

smcvb · 2024-10-07T11:17:52Z

@dependabot show org.springframework.boot:spring-boot-maven-plugin ignore conditions

dependabot · 2024-10-07T11:17:54Z

Ignore Conditions

Dependency	Ignore Condition
org.springframework.boot:spring-boot-maven-plugin	[>= 3.0.a, < 3.1]
org.springframework.boot:spring-boot-maven-plugin	[>= 3.a, < 4]

dependabot · 2024-10-07T11:18:48Z

Dependabot attempted to update this pull request, but because the branch dependabot/maven/maven-dependencies-2705db6d68 is protected it was unable to do so.

dependabot · 2024-10-07T11:18:48Z

Oh no! Something went wrong on our end. Please try again later.

If the problem persists, please contact GitHub support for assistance 🙇

smcvb · 2024-10-07T11:24:07Z

@dependabot recreate

dependabot · 2024-10-07T11:25:23Z

Dependabot attempted to update this pull request, but because the branch dependabot/maven/maven-dependencies-2705db6d68 is protected it was unable to do so.

dependabot · 2024-10-07T11:25:24Z

Oh no! Something went wrong on our end. Please try again later.

If the problem persists, please contact GitHub support for assistance 🙇

smcvb · 2024-10-07T11:28:11Z

Dependabot, for whatever reason, decided that ignored versions should be included.
As such, I have forcefully ignored all minor and major versions again for the misbehaving dependencies.

As GitHub is incapable of automatically recreating the PR, I will close it manually instead.
Let's assume next week Sunday (when Dependabot is triggered) we have fresh and working dependency upgrade PRs again.

dependabot · 2024-10-07T11:28:13Z

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

dependabot bot added Priority 1: Must Type: Dependency Upgrade labels Oct 6, 2024

dependabot bot requested review from a team, CodeDrivenMitch and smcvb and removed request for a team October 6, 2024 15:08

dependabot bot added this to the Release 4.11.0 milestone Oct 6, 2024

github-actions bot approved these changes Oct 6, 2024

View reviewed changes

smcvb self-assigned this Oct 7, 2024

smcvb closed this Oct 7, 2024

dependabot bot deleted the dependabot/maven/maven-dependencies-2705db6d68 branch October 7, 2024 11:28

smcvb added the Status: Won't Fix label Oct 7, 2024

smcvb removed this from the Release 4.11.0 milestone Oct 7, 2024

build(deps): bump the maven-dependencies group with 13 updates #534

build(deps): bump the maven-dependencies group with 13 updates #534

Conversation

dependabot bot commented on behalf of github Oct 6, 2024 • edited Loading

v5.0.0

Mockito 5: prepare for future JDK versions

Switch the default mockmaker to mockito-inline

When should I still be using the subclass mockmaker?

Update the minimum supported Java version to 11

What should I do if I still run JDK 8?

New type() method on ArgumentMatcher

v5.0.0

Mockito 5: prepare for future JDK versions

Switch the default mockmaker to mockito-inline

When should I still be using the subclass mockmaker?

Update the minimum supported Java version to 11

What should I do if I still run JDK 8?

New type() method on ArgumentMatcher

v5.0.0

Mockito 5: prepare for future JDK versions

Switch the default mockmaker to mockito-inline

When should I still be using the subclass mockmaker?

Update the minimum supported Java version to 11

What should I do if I still run JDK 8?

New type() method on ArgumentMatcher

v3.0.0

⭐ New Features

🐞 Bug Fixes

📔 Documentation

v3.0.0

⭐ New Features

🐞 Bug Fixes

📔 Documentation

v3.0.0

⭐ New Features

🐞 Bug Fixes

📔 Documentation

v3.0.0

⭐ New Features

🐞 Bug Fixes

📔 Documentation

v3.0.0

⭐ New Features

🐞 Bug Fixes

smcvb commented Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

smcvb commented Oct 7, 2024

smcvb commented Oct 7, 2024

dependabot bot commented on behalf of github Oct 7, 2024

dependabot bot commented on behalf of github Oct 6, 2024 •

edited

Loading

Switch the default mockmaker to `mockito-inline`

New `type()` method on `ArgumentMatcher`

Switch the default mockmaker to `mockito-inline`

New `type()` method on `ArgumentMatcher`

Switch the default mockmaker to `mockito-inline`

New `type()` method on `ArgumentMatcher`