V1.13.4 is out, thanks a lot to <@U01681FLZC2> as always and to a lot of new contributors! Several b...

# mockk

[Mattia Tommasone]

V1.13.4 is out, thanks a lot to @Adam S as always and to a lot of new contributors!
Several bugfixes included in the release, check it out! https://github.com/mockk/mockk/releases/tag/v1.13.4

[Klitos Kyriacou]

Thanks for the update. I see in the changelog that it should now be using Junit 5 instead of Junit 4. However, I still see Junit 4 when I do mvn dependency:tree in one of my projects that uses Mockk:

[INFO] \- io.mockk:mockk-jvm:jar:1.13.4:test
[INFO]    +- io.mockk:mockk-dsl-jvm:jar:1.13.4:test
[INFO]    +- io.mockk:mockk-agent-jvm:jar:1.13.4:test
[INFO]    |  +- org.objenesis:objenesis:jar:3.3:test
[INFO]    |  \- net.bytebuddy:byte-buddy-agent:jar:1.12.20:test
[INFO]    +- io.mockk:mockk-agent-api-jvm:jar:1.13.4:test
[INFO]    +- io.mockk:mockk-core-jvm:jar:1.13.4:test
[INFO]    \- junit:junit:jar:4.13.2:test
[INFO]       \- org.hamcrest:hamcrest-core:jar:1.3:test

[Adam S]

good spot - the PRs only updated the @Test annotation used for MockK tests. MockK still needs JUnit4 for its custom JUnit4 @Rule

[Klitos Kyriacou]

Thanks. If my application uses JUnit 5 for its tests, can I exclude junit:junit from the mockk library in my Maven pom.xml?

[Adam S]

yes, I should think so