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 junit-jupiter-engine from 5.7.2 to 5.8.0 #613

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 13, 2021

Bumps junit-jupiter-engine from 5.7.2 to 5.8.0.

Release notes

Sourced from junit-jupiter-engine's releases.

JUnit 5.8.0 = Platform 1.8.0 + Jupiter 5.8.0 + Vintage 5.8.0

See Release Notes.

JUnit 5.8.0-RC1 = Platform 1.8.0-RC1 + Jupiter 5.8.0-RC1 + Vintage 5.8.0-RC1

See Release Notes.

JUnit 5.8.0-M1 = Platform 1.8.0-M1 + Jupiter 5.8.0-M1 + Vintage 5.8.0-M1

See Release Notes.

Commits
  • 709fd6e Release 5.8
  • fa74055 Use text block
  • d36ea28 Declare service in module descriptor
  • 6c0bf02 Fix modular user guide tests by reading module jdk.httpserver
  • b6dff0d Add LauncherSessionListener example to user guide
  • 439084d Polish documentation for 5.8 GA
  • fa021ed Document published dependency scope change as potentially breaking
  • efb980c Polishing
  • 0bd6feb Remove link to package private class in Javadoc
  • 75538a7 Document that autoCloseArguments in @​ParameterizedTest is a potentially break...
  • 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 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)

Bumps [junit-jupiter-engine](https://github.com/junit-team/junit5) from 5.7.2 to 5.8.0.
- [Release notes](https://github.com/junit-team/junit5/releases)
- [Commits](junit-team/junit5@r5.7.2...r5.8.0)

---
updated-dependencies:
- dependency-name: org.junit.jupiter:junit-jupiter-engine
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 13, 2021
@coveralls
Copy link

Coverage Status

Coverage remained the same at 89.367% when pulling 6b0c69a on dependabot/maven/org.junit.jupiter-junit-jupiter-engine-5.8.0 into 7711b0d on master.

@hazendaz hazendaz self-assigned this Sep 13, 2021
@hazendaz hazendaz merged commit 3b4b3f0 into master Sep 13, 2021
@dependabot dependabot bot deleted the dependabot/maven/org.junit.jupiter-junit-jupiter-engine-5.8.0 branch September 13, 2021 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants