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

fix(deps): update dependency io.kotest:kotest-assertions-core to v5 #29

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 1, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
io.kotest:kotest-assertions-core 4.6.3 -> 5.9.1 age adoption passing confidence

Test plan: CI should pass with updated dependencies. No review required: this is an automated dependency update PR.


Release Notes

kotest/kotest (io.kotest:kotest-assertions-core)

v5.9.1

What's Changed
Assertions
Framework
Property-testing
Docs
Build / CI/CD / Dependency updates
New Contributors

Full Changelog: kotest/kotest@v5.9.0...v5.9.1

v5.9.0

Highlights

Support for wasmJs has been added, curtesy of @​OliverO2

What's Changed

New Contributors

Full Changelog: kotest/kotest@v5.8.1...v5.9.0

v5.8.1

What's Changed
New Contributors

Full Changelog: kotest/kotest@v5.8.0...v5.8.1

v5.8.0

What's Changed
New Contributors

Full Changelog: kotest/kotest@v5.7.2...v5.8.0

v5.7.2

v5.7.1

v5.7.0

v5.6.2

5.6.2 May 2023

Assertions
Property testing
Documentation
Other

⚠️ Reverted behavior of Arb.string()

With Kotest 5.6.0, Codepoint.ascii() was changed to include a wider range of ascii chararacters, and Codepoint.printableAscii() was introduced with the historic range used by Codepoint.ascii().

Arb.string() has been using Codepoint.ascii() as it's default for generating chars for the string. This caused issues for some users, and we decided to revert Arb.string() to the historic behavior by changing the default to the new Codepoint.printableAscii().

Hopefully this doesn't cause any issues for you. If it does, you can revert to the 5.6.0 ~ 5.6.1 behavior by using Codepoint.ascii() explicitly.

If you added explicit usage of Codepoint.printableAscii() to circumvent the issue, you can safely remove the explicit parameter starting with Kotest 5.6.2.

New Contributors

Full Changelog: kotest/kotest@v5.6.1...v5.6.2

v5.6.1

Maintenance release, published since 5.6.0 failed to upload for some targets.

Breaking changes (from 5.5.5 -> 5.6.x)
  • Moved ConstantNow-related functions to a new module named io.kotest:kotest-extensions-now (remember to add -jvm suffix for Maven)
    • Add this module as a dependency to keep using withConstantNow
  • Remove Iterable checking logic from IterableEq (#​3420)

See full changelog at https://kotest.io/docs/changelog.html

v5.6.0

Breaking changes
  • Moved ConstantNow-related functions to a new module named io.kotest:kotest-extensions-now (remember to add -jvm suffix for Maven)
    • Add this module as a dependency to keep using withConstantNow
  • Remove Iterable checking logic from IterableEq (#​3420)

See full changelog at https://kotest.io/docs/changelog.html

v5.5.5

  • Support coroutineTestScope globally (#​3383)
  • Improved double and float tolerance messages (#​3355)
  • Nested Data Driven Tests is not displayed as nested in Intellij #​3341
  • Fixed writing seeds when test name contains a colon on windows (#​3304)
  • withClue() fails with EmptyStackException if a coroutine switches threads #​2447
  • Use TestDispatcher inside beforeInvocation callbacks (#​3363)
  • Make checkCoverage checking against provided pairs (#​3344)
  • Kotest runner junit5 jvm has vulnerable transative dependency CVE-2021-29425 #​3364
  • Fix sequence matchers for constrained sequences (#​3336)
  • Print full path in JunitXmlReporter when useTestPathAsName is enabled instead of just leaf and first parent #​3347
  • Support { } lambdas as lazy clues (#​3348)
  • Use 'language injection' on assertions, so embedded languages are easier to use in IntelliJ #​2916
  • Removing default location for htmlReporter and using the default value from the constructor (#​3306)
  • Arb.bigDecimal should generate decimals which terminate with all kinds of terminal digit #​3282
  • Check enums using equals method instead of scanning their properties (#​3291)
  • Add BlockHound support (#​3308)
  • Matchers return this. (#​2945)
  • Added shouldMatchResource, shouldNotMatchResource matchers (#​2945)
  • Added matchExactly matcher for Maps #​3246
  • Fix dumping config when systemProperty set to true (#​3275)
  • Returning the original failure when ErrorCollector has only collected a single failure (#​3269)

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:

v5.5.3: 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 https://github.com/kotest/kotest/pull/3257
Tag inheritance configuration is now available on AbstractProjectConfig

v5.5.1: 5.5.1

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

v5.5.0

v5.4.2: 5.4.2

v5.4.1

v5.3.0

v5.2.2

v5.0.1

https://kotest.io/docs/changelog.html


Configuration

📅 Schedule: Branch creation - "on the 1st through 7th day of the month" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the bot label Dec 1, 2021
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from bc0971f to 7491c61 Compare December 10, 2021 13:47
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 7491c61 to 75b466c Compare December 19, 2021 08:06
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 75b466c to da25827 Compare January 17, 2022 11:22
@renovate renovate bot changed the title Update dependency io.kotest:kotest-assertions-core to v5 chore(deps): update dependency io.kotest:kotest-assertions-core to v5 Mar 12, 2022
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch 2 times, most recently from 88e5aaa to 8fb1c21 Compare March 14, 2022 17:10
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 8fb1c21 to 3f7bba1 Compare March 28, 2022 04:24
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 3f7bba1 to 34ac783 Compare April 9, 2022 19:01
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 34ac783 to 125cdf7 Compare May 15, 2022 22:57
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch 2 times, most recently from f562ecf to f03e6fc Compare June 25, 2022 09:04
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch 2 times, most recently from e683c61 to 9c55871 Compare July 28, 2022 10:59
@renovate renovate bot changed the title chore(deps): update dependency io.kotest:kotest-assertions-core to v5 fix(deps): update dependency io.kotest:kotest-assertions-core to v5 Aug 1, 2022
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 9c55871 to 4c92197 Compare August 10, 2022 19:44
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 4c92197 to 6edc4cc Compare November 20, 2022 19:01
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 6edc4cc to fce2f8e Compare March 16, 2023 09:49
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from fce2f8e to 2150ea9 Compare April 17, 2023 10:26
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 2150ea9 to cf7a900 Compare May 28, 2023 11:19
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from cf7a900 to 92c9a14 Compare July 20, 2023 18:38
@renovate renovate bot changed the title fix(deps): update dependency io.kotest:kotest-assertions-core to v5 Update dependency io.kotest:kotest-assertions-core to v5 Jul 20, 2023
@renovate renovate bot changed the title Update dependency io.kotest:kotest-assertions-core to v5 fix(deps): update dependency io.kotest:kotest-assertions-core to v5 Aug 8, 2023
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch 3 times, most recently from c3dd600 to 1a50360 Compare September 5, 2023 21:42
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 1a50360 to 44b75f5 Compare November 3, 2023 22:34
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 44b75f5 to 010c5f8 Compare February 2, 2024 10:52
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 010c5f8 to 874b933 Compare March 11, 2024 06:57
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 874b933 to 12fd0a9 Compare May 9, 2024 21:16
@renovate renovate bot force-pushed the renovate/io.kotest-kotest-assertions-core-5.x branch from 12fd0a9 to e59696c Compare June 6, 2024 12:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants