Skip to content

Bump org.junit.platform:junit-platform-launcher from 6.0.3 to 6.1.0 #406

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
docwho2 merged 1 commit into from
May 19, 2026
+1 −1
Merged

Bump org.junit.platform:junit-platform-launcher from 6.0.3 to 6.1.0 #406

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pom.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@
<dependency>
<groupId>org.junit.platform</groupId>
<artifactId>junit-platform-launcher</artifactId>
<version>6.0.3</version>
<version>6.1.0</version>
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep JUnit artifacts on one aligned version

Updating only junit-platform-launcher to 6.1.0 while org.junit:junit-bom remains at 6.0.3 introduces mixed JUnit runtime versions (for example, integration-test pulls junit-jupiter-engine from the BOM but junit-platform-launcher from this override). JUnit 6 artifacts are expected to be version-aligned, and this mismatch can surface as runtime incompatibilities during test discovery/execution (e.g., linkage errors) in modules that use both launcher and Jupiter engine.

Useful? React with 👍 / 👎.

</dependency>

</dependencies>
Expand Down
Loading