Skip to content

Update kotest to 6.2.4, and drop the module it absorbed - #56

Merged
Jake-Moore merged 1 commit into
mainfrom
chore/kotest-6
Sep 4, 2026
Merged

Update kotest to 6.2.4, and drop the module it absorbed#56
Jake-Moore merged 1 commit into
mainfrom
chore/kotest-6

Conversation

@Jake-Moore

Copy link
Copy Markdown
Owner

io.kotest:kotest-framework-datatest was never published past 5.9.1. Its contents moved into
kotest-framework-engine, which already arrives transitively through kotest-runner-junit5, so
there is nothing to migrate to and nothing to replace it with.

Renovate moved every kotest artifact together through the shared version reference and asked for a
coordinate that does not exist, so #52 failed at dependency resolution before compiling anything.
That is why it failed in two minutes rather than the four a real test run takes:

Could not find io.kotest:kotest-framework-datatest:6.2.4.

It was never used

There is no io.kotest.datatest import and no withData anywhere in either test source set. It has
been an unused dependency for as long as it has been declared, and it only became visible when it
stopped existing.

Nothing else in the major needed changing

KotestConfig extends AbstractProjectConfig and sets a spec execution order, which is the kind of
API that usually moves in a framework major. It did not. No call site changed, and the run produces
no kotest deprecation warnings.

Verified against the authoritative Maven metadata rather than the search index, which is stale and
still reports 6.0.0.M4 as newest:

artifact latest 6.x
kotest-runner-junit5 6.2.4 yes
kotest-assertions-core 6.2.4 yes
kotest-property 6.2.4 yes
kotest-framework-engine 6.2.4 yes
kotest-framework-datatest 5.9.1 none

And that io/kotest/datatest/ really is inside kotest-framework-engine-jvm-6.2.4.jar.

Tests

319 green, detekt clean.

Supersedes #52, which cannot pass as generated.

io.kotest:kotest-framework-datatest was never published past 5.9.1. Its contents
moved into kotest-framework-engine, which already arrives transitively through
kotest-runner-junit5, so there is nothing to migrate to and nothing to replace it
with.

Renovate moved every kotest artifact together through the shared version reference
and asked for a coordinate that does not exist, so the build failed at dependency
resolution before compiling anything. That is why it failed in two minutes rather
than the four a real test run takes.

Nothing here ever used it. There is no io.kotest.datatest import and no withData
in either test source set, so it has been an unused dependency for as long as it
has been declared, and only became visible when it stopped existing.

Nothing else in the major needed changing. AbstractProjectConfig and the spec
execution order it sets are unchanged, no call site moved, and the run produces no
deprecation warnings.

319 tests green, detekt clean.

Co-Authored-By: Claude Code <[email protected]>
@coderabbitai

coderabbitai Bot commented Sep 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 32 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: 5e08b57a-2b3a-49dc-8a74-4265c9f42a1a

📥 Commits

Reviewing files that changed from the base of the PR and between b486b0f and 6d4889b.

📒 Files selected for processing (3)
  • core-api/build.gradle.kts
  • gradle/libs.versions.toml
  • plugin-api/build.gradle.kts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@Jake-Moore
Jake-Moore merged commit 37d9db8 into main Sep 4, 2026
2 checks passed
@Jake-Moore
Jake-Moore deleted the chore/kotest-6 branch September 4, 2026 06:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant