Bump org.junit.jupiter:junit-jupiter-api from 5.10.1 to 6.0.3#29
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
Bump org.junit.jupiter:junit-jupiter-api from 5.10.1 to 6.0.3#29dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [org.junit.jupiter:junit-jupiter-api](https://github.com/junit-team/junit-framework) from 5.10.1 to 6.0.3. - [Release notes](https://github.com/junit-team/junit-framework/releases) - [Commits](junit-team/junit-framework@r5.10.1...r6.0.3) --- updated-dependencies: - dependency-name: org.junit.jupiter:junit-jupiter-api dependency-version: 6.0.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
dependabot
bot
added
dependencies
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| implementation 'org.springframework.boot:spring-boot-starter-web:3.2.0' | ||
|
|
||
| testImplementation 'org.junit.jupiter:junit-jupiter-api:5.10.1' | ||
| testImplementation 'org.junit.jupiter:junit-jupiter-api:6.0.3' |
There was a problem hiding this comment.
🔴 JUnit Jupiter API and Engine major version mismatch will break tests
The junit-jupiter-api was bumped to 6.0.3 but junit-jupiter-engine remains at 5.8.1 (build.gradle:18). These two artifacts are part of the same JUnit Jupiter project and must be version-aligned — the engine is responsible for discovering and running tests written against the API. A major version mismatch (6.x API vs 5.x engine) will cause test runtime failures, as the 5.x engine won't be able to execute tests compiled against the 6.x API.
Prompt for agents
In build.gradle, the junit-jupiter-api (line 17) was changed to version 6.0.3, but junit-jupiter-engine (line 18) is still at 5.8.1. These must be kept in sync. Either revert the API back to a 5.x version matching the engine (e.g., both at 5.10.1), or update the engine to the same version as the API. Ensure both junit-jupiter-api and junit-jupiter-engine use the same version.
Was this helpful? React with 👍 or 👎 to provide feedback.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps org.junit.jupiter:junit-jupiter-api from 5.10.1 to 6.0.3.
Release notes
Sourced from org.junit.jupiter:junit-jupiter-api's releases.
... (truncated)
Commits
36e3253Release 6.0.3295561fFinalize 6.0.3 release notesea18076Fix deadlock in NamespacedHierarchicalStore.computeIfAbsent() (#5348)869e232Add 5.14.3 release notesd4b34c4Fix links to User Guide5c8fb0fReliably support JRE.OTHER with @EnabledOnJre and @DisabledOnJrefebb13fCheck out entire repo so switching tomainbranch works in last step71fba90Installpoppler-utilsforpdfinfo740e9e0Update API baseline2ba535fUse release branch of examples repoDependabot 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)