Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Bump org.junit.jupiter:junit-jupiter-api from 5.11.1 to 5.11.2 #444

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 7, 2024

Bumps org.junit.jupiter:junit-jupiter-api from 5.11.1 to 5.11.2.

Release notes

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

JUnit 5.11.2 = Platform 1.11.2 + Jupiter 5.11.2 + Vintage 5.11.2

See Release Notes.

Full Changelog: junit-team/junit5@r5.11.1...r5.11.2

Commits
  • 5b1a6d1 Release 5.11.2
  • b7816b6 Finalize 5.11.2 release notes
  • f8e22c7 Finalize 5.10.5 release notes
  • 8e63938 Remove reference to 5.10.4 in 5.11.2 release notes
  • 7e9d728 Document #4043 in 5.10.5 release notes
  • c11f224 Create initial 5.10.5 release notes from template
  • ab94140 Fix global read-write lock handling when not declared on top level
  • 9658fac Add initial 5.11.2 release notes from template
  • 5f52ced Fix link to milestone page
  • 558f480 Back to snapshots for further development
  • See full diff in compare view

Dependabot compatibility score

You can trigger a rebase of this PR 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 Oct 7, 2024
@violetagg
Copy link
Member

@dependabot rebase

Bumps [org.junit.jupiter:junit-jupiter-api](https://github.com/junit-team/junit5) from 5.11.1 to 5.11.2.
- [Release notes](https://github.com/junit-team/junit5/releases)
- [Commits](junit-team/junit5@r5.11.1...r5.11.2)

---
updated-dependencies:
- dependency-name: org.junit.jupiter:junit-jupiter-api
  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/org.junit.jupiter-junit-jupiter-api-5.11.2 branch from 0032753 to a995c2e Compare October 7, 2024 08:14
@violetagg violetagg merged commit ac521bc into master Oct 7, 2024
2 checks passed
@violetagg violetagg added this to the 1.0.10.RELEASE milestone Oct 7, 2024
@dependabot dependabot bot deleted the dependabot/gradle/org.junit.jupiter-junit-jupiter-api-5.11.2 branch October 7, 2024 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/dependency-upgrade A dependency upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants