build(deps): bump org.junit.jupiter:junit-jupiter-engine from 5.12.2 to 6.0.3#2038
Conversation
Bumps [org.junit.jupiter:junit-jupiter-engine](https://github.com/junit-team/junit-framework) from 5.12.2 to 6.0.3. - [Release notes](https://github.com/junit-team/junit-framework/releases) - [Commits](junit-team/junit-framework@r5.12.2...r6.0.3) --- updated-dependencies: - dependency-name: org.junit.jupiter:junit-jupiter-engine dependency-version: 6.0.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
Closing this PR as JUnit Jupiter 6.x requires Java 17+ (class file version 61.0), which violates MockServer's Java 11 compatibility policy. Why this fails:
MockServer's Java 11 policy: JUnit Jupiter version compatibility:
Current version: JUnit Jupiter 5.12.2 is the latest version compatible with Java 11. We will continue to accept JUnit Jupiter 5.x patch and minor version updates, but cannot accept the 6.x major version upgrade until MockServer's minimum Java version is raised to 17+. |
|
Closing due to Java 11 incompatibility (see comment above). |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps org.junit.jupiter:junit-jupiter-engine from 5.12.2 to 6.0.3.
Release notes
Sourced from org.junit.jupiter:junit-jupiter-engine'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)