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

Upgrade JUnit Jupiter 5.9.1 -> 5.9.2 #457

Merged
merged 1 commit into from
Jan 11, 2023

Conversation

Picnic-Bot
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
org.junit:junit-bom (source) import patch 5.9.1 -> 5.9.2

  • If you want to rebase/retry this PR, check this box

@Picnic-Bot
Copy link
Contributor Author

Suggested commit message:

Upgrade JUnit 5.9.1 -> 5.9.2

@github-actions
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

1 similar comment
@github-actions
Copy link

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

@Stephan202 Stephan202 added this to the 0.8.0 milestone Jan 11, 2023
Copy link
Member

@Stephan202 Stephan202 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested commit message:

Upgrade JUnit Jupiter 5.9.1 -> 5.9.2 (#457)

See:
- https://junit.org/junit5/docs/current/release-notes/index.html
- https://github.com/junit-team/junit5/releases/tag/r5.9.2
- https://github.com/junit-team/junit5/compare/r5.9.1...r5.9.2

Also left a comment for some further follow-up.

@rickie rickie changed the title Upgrade org.junit:junit-bom 5.9.1 -> 5.9.2 Upgrade JUnit Jupiter 5.9.1 -> 5.9.2 Jan 11, 2023
@rickie rickie merged commit 8e24da9 into master Jan 11, 2023
@rickie rickie deleted the renovate/org.junit-junit-bom-5.x branch January 11, 2023 10:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants