Bump junit-jupiter.version from 5.10.0 to 5.10.1

[dependabot]

Bumps junit-jupiter.version from 5.10.0 to 5.10.1.
Updates org.junit:junit-bom from 5.10.0 to 5.10.1

Release notes

Sourced from org.junit:junit-bom's releases.

JUnit 5.10.1 = Platform 1.10.1 + Jupiter 5.10.1 + Vintage 5.10.1

See Release Notes.

Full Changelog: junit-team/junit5@r5.10.0...r5.10.1

Commits

• e5f50d8 Release 5.10.1
• ac86d18 Fix typo in AfterAll documentation
• 388c5be Harmonize application of method and field filters in search algorithms
• f82dd1e Apply field predicate before searching type hierarchy
• 1d1eb85 Polishing
• 5ce280e Update picocli to 4.7.5 and enable help width computation
• fea05c3 Fix ConsoleLauncherTests and StandaloneTests
• c556735 Use same expected files for all JDK versions
• 808493a Run StandaloneTests for Java 8 under Java 8
• 9ec5766 Unify messages about exit codes in StandaloneTests
• Additional commits viewable in compare view

Updates org.junit.jupiter:junit-jupiter-api from 5.10.0 to 5.10.1

Release notes

Sourced from org.junit.jupiter:junit-jupiter-api's releases.

JUnit 5.10.1 = Platform 1.10.1 + Jupiter 5.10.1 + Vintage 5.10.1

See Release Notes.

Full Changelog: junit-team/junit5@r5.10.0...r5.10.1

Commits

• e5f50d8 Release 5.10.1
• ac86d18 Fix typo in AfterAll documentation
• 388c5be Harmonize application of method and field filters in search algorithms
• f82dd1e Apply field predicate before searching type hierarchy
• 1d1eb85 Polishing
• 5ce280e Update picocli to 4.7.5 and enable help width computation
• fea05c3 Fix ConsoleLauncherTests and StandaloneTests
• c556735 Use same expected files for all JDK versions
• 808493a Run StandaloneTests for Java 8 under Java 8
• 9ec5766 Unify messages about exit codes in StandaloneTests
• Additional commits viewable in compare view

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

1. Register at Qodana Cloud and configure the action
2. Use GitHub Code Scanning with Qodana
3. Host Qodana report at GitHub Pages
4. Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2023.2.8
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions