norm Bump kotest-runner-junit5-jvm from 4.6.2 to 5.5.4

Bumps kotest-runner-junit5-jvm from 4.6.2 to 5.5.4.

Release notes

Sourced from kotest-runner-junit5-jvm's releases.

v5.5.4

Fixes issue 3277.

gradle test --tests "A*" --tests "B*"

All tests from A* and B* were skipped instead of being ran.

This was a regression from 5.4.x, where this used to work. This was because kotest 5.5.3 were using the wrong combinators for combining the inclusion filters.

Contributors:

@myuwono

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.

... (truncated)

Commits

3f568e4 fix gradle include combinator (#3278)
d74dce5 Reducing flakiness of ContainerTimeoutTest, hopefully
c10b832 Adding JVM SpecInterceptor reclassifying aborted tests as Ignored (#3268)
2f57f2e Adjusting error message to correctly state missing/extra keys (#3267)
e0ca769 typo (#3266)
632ac87 Read/write table data to a file (#3197)
0ab1b52 Update jupiter to 5.8.2 (#3264)
55257df Update annotations.md (#3259)
d71a344 removed release_bom.yml that was used to get kotest-bom 5.5.1 out
4a91954 add infix to shouldHaveSameHashCodeAs (#3258)
Additional commits viewable in compare view

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)