Skip to content
New issue

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

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

Already on GitHub? # to your account

Bump org.junit:junit-bom from 5.10.3 to 5.10.4 #3214

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 25, 2024

Bumps org.junit:junit-bom from 5.10.3 to 5.10.4.

Release notes

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

JUnit 5.10.4 = Platform 1.10.4 + Jupiter 5.10.4 + Vintage 5.10.4

See Release Notes.

Full Changelog: junit-team/junit5@r5.10.3...r5.10.4

Commits
  • c300b73 Release 5.10.4
  • 59f01bb Fix integration tests running Maven on JDK 24
  • e60653d Fix Develocity access key injection
  • 847de89 Finalize 5.10.4 release notes
  • 611ae8d Fix tests after cherry-picking changes from main branch
  • 499fb2b Update "since" for backported JRE constants
  • 668e12f Fix syntax for old way of passing arguments
  • 9ffd4a7 Add build for JDK 21
  • c6de4b0 Use old Gradle property
  • 334c1a5 Remove OpenJ9 build
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

@dependabot dependabot bot added the type: dependency-upgrade A dependency upgrade label Sep 25, 2024
@github-actions github-actions bot added this to the 3.4.0-M3 milestone Sep 25, 2024
@spring-builds spring-builds enabled auto-merge (rebase) September 25, 2024 03:31
@rwinch
Copy link
Member

rwinch commented Sep 26, 2024

@dependabot rebase

Bumps [org.junit:junit-bom](https://github.com/junit-team/junit5) from 5.10.3 to 5.10.4.
- [Release notes](https://github.com/junit-team/junit5/releases)
- [Commits](junit-team/junit5@r5.10.3...r5.10.4)

---
updated-dependencies:
- dependency-name: org.junit:junit-bom
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/gradle/main/org.junit-junit-bom-5.10.4 branch from 31a3cac to 76cf467 Compare September 26, 2024 16:00
@spring-builds spring-builds merged commit efe7b32 into main Sep 26, 2024
4 checks passed
@dependabot dependabot bot deleted the dependabot/gradle/main/org.junit-junit-bom-5.10.4 branch September 26, 2024 16:11
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
type: dependency-upgrade A dependency upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants