4.0.2

• the exception thrown when more than one candidate bean names for SpykBean were found didn't align with the one thrown by Spring Boot's native Mockito support. Now it does. See #100

4.0.1

• fix #97: memory leak in com.ninjasquad.springmockk.MockkClear. In projects where many different Spring contextx are created during tests, even though the Spring test context caches ends up destroying old ones, SpringMockK retained references to mocks, themselves retaining references to the Spring context, and leading to high memory usage. SpringMockK now uses weak references in order to not prevent the garbage collector to collect those mocks if they're only referenced by SpringMockK, for clearing purposes.

4.0.0

SpringMockK 4.0.0 is built against Spring Boot 3, with Java 17, and MockK 1.13.3.

Spying JDK proxies with Java 17 requires to pass a specific option to the JVM. See the README for details.

Important note: MockKs artifact ID has been modified from mockk to mockk-jvm. If you specify a specific version for MockK in your build rather than relying on SpringMockK's transitive dependency, make sure to use the new arctifact ID.

3.1.2

• fix #90: issue with verifyAll failing when using constructor injection

3.1.1

• report fix from Spring Boot

3.1.0

• report fix from Spring Boot
• use MockK 1.12.1 (closes #68)

3.0.1

• fix #56 : publish the gradle module metadata.

3.0.0

• Upgrade to Spring Boot 2.4.0. Please keep using version 2.x of SpringMockK if you still use Spring Boot 2.2.x or 2.3.x. Changes made in Spring Boot Mockito's support in 2.4.0 have ben ported to SpringMockK. The main new feature being to be able to use nested JUnit 5 tests. \o/
• Upgrade to MockK 1.10.2

2.0.3

fix #44: Spring context is not being reloaded when it shouldn't be anymore. This was actually a Spring Boot bug. The fix in Spring Boot has been reported here.

2.0.2

This release contains bug fixes that have been reported from Spring Boot