chore(deps): bump org.junit.vintage:junit-vintage-engine from 5.9.2 to 6.1.3 - #45
Conversation
Bumps [org.junit.vintage:junit-vintage-engine](https://github.com/junit-team/junit-framework) from 5.9.2 to 6.1.3. - [Release notes](https://github.com/junit-team/junit-framework/releases) - [Commits](junit-team/junit-framework@r5.9.2...r6.1.3) --- updated-dependencies: - dependency-name: org.junit.vintage:junit-vintage-engine dependency-version: 6.1.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 0bb1969. Configure here.
| implementation 'org.springframework.boot:spring-boot-starter-webflux' | ||
| implementation 'org.springframework.boot:spring-boot-starter-validation' | ||
| implementation 'org.junit.vintage:junit-vintage-engine:5.9.2' | ||
| implementation 'org.junit.vintage:junit-vintage-engine:6.1.3' |
There was a problem hiding this comment.
Incompatible JUnit major version bump
High Severity
Bumping junit-vintage-engine alone to 6.1.3 breaks alignment with Spring Boot 3.0.4, which still manages JUnit Jupiter 5.9.2 and Platform 1.9.2 via spring-boot-starter-test. JUnit 6 requires Platform, Jupiter, and Vintage to share the same major line, so the test classpath can fail engine discovery or load with linkage errors when ./gradlew test runs.
Reviewed by Cursor Bugbot for commit 0bb1969. Configure here.
Bumps org.junit.vintage:junit-vintage-engine from 5.9.2 to 6.1.3.
Release notes
Sourced from org.junit.vintage:junit-vintage-engine's releases.
... (truncated)
Commits
f59f60dRelease 6.1.3cd8ec92Finalize 6.1.3 release notesc8729f2Restore compatibility with GraalVM 25 (#5901)ddc9e74Update graalvm/setup-graalvm action to v1.6.4 (#5959)fe2c52aUpdate plugin org.graalvm.buildtools.native to v1.1.7 (#5923)62afc02Delay GraalVM plugin updates for 3 days0cc2902SkipgraalVmTesttask if GraalVM env vars are not setf6bbfc5Move GraalVM tests to separate test task (#5903)e87e052Update plugin org.graalvm.buildtools.native to v1.1.6 (#5899)1cd56dfUpdate plugin org.graalvm.buildtools.native to v1.1.5 (#5880)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Medium Risk
A major-version test dependency bump can affect Gradle resolution and any legacy JUnit 4 tests; current tests are Jupiter-only so runtime impact should be limited if CI passes.
Overview
Bumps
org.junit.vintage:junit-vintage-engineinbuild.gradlefrom 5.9.2 to 6.1.3 (JUnit 5 → 6 major line). No other build or source files change; tests still run viauseJUnitPlatform()and existing suites use JUnit Jupiter, not Vintage/JUnit 4.Reviewed by Cursor Bugbot for commit 0bb1969. Configure here.