Fix pitest dependency resolution with stable runtime version

[vamsimanohar]

Summary

• The pitest Gradle plugin 1.19.0-rc.2 is needed for Gradle 9 compatibility, but its matching RC runtime artifacts (org.pitest:pitest-command-line:1.19.0-rc.2) are not published to Maven Central, causing Could not find org.pitest:pitest-command-line:1.19.0-rc.2 errors when running ./gradlew :core:pitest.
• This PR decouples the plugin version from the runtime version by setting pitestVersion = '1.22.1' (latest stable release available on Maven Central) and updating junit5PluginVersion to 1.2.1.
• Verified locally: pitest resolves all dependencies from mavenCentral() and completes mutation testing successfully (8279 mutations generated, 3750 killed, 74% test strength).

Related GitHub issues

• szpak/gradle-pitest-plugin#380 — stable 1.19.0 not yet released
• szpak/gradle-pitest-plugin#386 — rc.2 task configuration problem
• szpak/gradle-pitest-plugin#385 — NoClassDefFoundError with rc.2

Test plan

• ./gradlew :core:pitest completes successfully (BUILD SUCCESSFUL in 5m 17s)
• CI passes

🤖 Generated with Claude Code

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated Pitest integration to version 1.22.1.
  • Updated JUnit 5 plugin version for Pitest to 1.2.1.

Walkthrough

Updates Pitest and JUnit5 plugin versions in the build configuration. Pitest plugin and task configuration versions are incremented from 1.19.0-rc.2 to 1.22.1, and JUnit5 plugin version is updated from 1.0.0 to 1.2.1.

Changes

Cohort / File(s)	Summary
Dependency Version Updates core/build.gradle	Bumped Pitest plugin from 1.19.0-rc.2 to 1.22.1, pitestVersion configuration from 1.19.0-rc.2 to 1.22.1, and JUnit5 plugin version from 1.0.0 to 1.2.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: decoupling pitest plugin from runtime version and fixing dependency resolution by using a stable runtime version.
Description check	✅ Passed	The description is comprehensive and directly related to the changeset, explaining the problem, solution, verification steps, and referencing related issues.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/pitest-stable-runtime-version

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

core/build.gradle (1)

29-29: ⚠️ Potential issue | 🟡 Minor

Consider upgrading gradle-pitest-plugin to 1.19.0-rc.3 and verify JUnit 5 plugin compatibility.

The versions are valid: pitest 1.22.1 (released Feb 2, 2026) and pitest-junit5-plugin 1.2.1 are both available on Maven Central. However:

1. gradle-pitest-plugin 1.19.0-rc.3 (Jan 19, 2026) is now available, newer than the 1.19.0-rc.2 in line 29. Consider upgrading if it doesn't require Gradle version changes.

2. The gradle-pitest-plugin maintainer notes that "in some cases there could be some issues when using non-default PIT versions." While pitest 1.22.1 is compatible in practice with the plugin, monitor for any runtime issues with mutation testing.

3. pitest-junit5-plugin 1.2.1 is compatible with pitest 1.22.1 (requires pitest ≥ 1.15.2), but ensure that the junit-platform-launcher version is aligned to avoid JUnit platform API mismatches.