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

chore(deps): bump kotest-runner-junit5 from 4.6.0 to 5.5.3 #173

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 28, 2022

Bumps kotest-runner-junit5 from 4.6.0 to 5.5.3.

Release notes

Sourced from kotest-runner-junit5's releases.

5.5.3

Updated JUnit version from 5.7.2 to 5.8.2

Kotest now requires the runtime version of JUnit to be at least 5.8

Note: If your build somehow manages to put both JUnit 5.7 and 5.8 onto the classpath and they load in the wrong order, you might see problems related to ClassOrderer not being found. Please make sure that only JUnit 5.8+ is loaded

v5.5.2

Gradle test filter fixes, by @​myuwono kotest/kotest#3257 Tag inheritance configuration is now available on AbstractProjectConfig

5.5.1

Fixed an issue where tests where being skipped when filtered out by the full spec name

v5.5.0

No release notes provided.

5.4.2

No release notes provided.

v5.4.1

No release notes provided.

v5.4.0

No release notes provided.

v5.3.0

No release notes provided.

v5.2.3

No release notes provided.

v5.2.2

No release notes provided.

v5.2.1

No release notes provided.

v5.2.0

No release notes provided.

v5.1.0

No release notes provided.

v5.0.3

No release notes provided.

v5.0.2

No release notes provided.

... (truncated)

Commits

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 [kotest-runner-junit5](https://github.com/kotest/kotest) from 4.6.0 to 5.5.3.
- [Release notes](https://github.com/kotest/kotest/releases)
- [Commits](kotest/kotest@v4.6.0...v5.5.3)

---
updated-dependencies:
- dependency-name: io.kotest:kotest-runner-junit5
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Oct 28, 2022
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 4, 2022

Superseded by #175.

@dependabot dependabot bot closed this Nov 4, 2022
@dependabot dependabot bot deleted the dependabot/gradle/io.kotest-kotest-runner-junit5-5.5.3 branch November 4, 2022 03:12
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.

0 participants