Kotest 4.6.1 pulls kotlin version up to 1.5.0
See original GitHub issueHi, I read this bit in your release notes where you wanted to support multiple kotlin versions:
The kotlin stdlib dependencies are now marked as compileOnly, meaning the version in your build will be used. Kotest tries to maintain compatibility across multiple versions by not relying on features only available in the latest releases.
But on trying it I noticed that I was still getting a dependency on kotlin 1.5.0 libraries.
Specifically I see that
io.kotest:kotest-runner-junit5-jvm:4.6.1
has an api dependency on org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm:1.5.0
which in turn pulls in the 1.5.0 stdlib
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Changelog - Kotest
The kotlin stdlib dependencies are now marked as compileOnly , meaning the version in your build will be used. Kotest tries to maintain...
Read more >When running individual unit test using WordSpec, getting ...
Which version of Kotest are you using Plugin version 1.1.36-IC-2021.1 kotest version 4.5.0 kotlin version 1.5.0 Try the following test, see that test...
Read more >Kotlin releases
We ship different types of releases: Feature releases (1.x) that bring major changes in the language. Incremental releases (1.x.y) that are shipped between ......
Read more >Upgrading Android kotlin version to 1.5.0 throwing error ...
I had this issue while upgrading Kotlin version to 1.6.10 ... depends on new kotlin changes in version 1.5.0 and try to update...
Read more >sksamuel on Twitter: "Kotest 4.6 released with support for Kotlin 1.5 ...
Kotest 4.6 released with support for Kotlin 1.5. https://kotest.io #kotlin #testing · 2:23 AM · May 19, 2021 ·Twitter Web App.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok yes I would consider this a bug. We shall release 4.6.2 with this reverted. Thanks for letting us know.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.