This repository was archived by the owner on May 8, 2024. It is now read-only.
fix(deps): update dependency io.kotest:kotest-assertions-core to v5.8.1#57
Open
renovate[bot] wants to merge 1 commit intomainfrom
Open
fix(deps): update dependency io.kotest:kotest-assertions-core to v5.8.1#57renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
1304bbb to
eba8845
Compare
eba8845 to
87ebaa3
Compare
87ebaa3 to
055f531
Compare
055f531 to
95e7564
Compare
95e7564 to
ecc3039
Compare
ecc3039 to
6582d78
Compare
6582d78 to
9ea2264
Compare
9ea2264 to
42a14d6
Compare
8a63362 to
38bc9ce
Compare
38bc9ce to
5753109
Compare
5753109 to
f78ce7b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.4.2->5.8.1Release Notes
kotest/kotest (io.kotest:kotest-assertions-core)
v5.8.1What's Changed
Longassertions and property testers by @RusticFlare in https://github.com/kotest/kotest/pull/3720BigDecimal.ZERO.shouldBePositive()returning true by @pubiqq in https://github.com/kotest/kotest/pull/3814intersectmatcher to ranges by @AlexCue987 in https://github.com/kotest/kotest/pull/3792shouldNotBePositiveandshouldNotBeNegativematchers for BigDecimal by @pubiqq in https://github.com/kotest/kotest/pull/3818IterableinwithDataon root level by @obecker in https://github.com/kotest/kotest/pull/3831shouldBe expectedequivalent toshould be(expected)for non-matcher objects by @pubiqq in https://github.com/kotest/kotest/pull/3827New Contributors
Full Changelog: kotest/kotest@v5.8.0...v5.8.1
v5.8.0What's Changed
New Contributors
Full Changelog: kotest/kotest@v5.7.2...v5.8.0
v5.7.2v5.7.1v5.7.0v5.6.25.6.2 May 2023
Assertions
Property testing
Arb.string()to only generate Strings of printable ascii charactersDocumentation
Other
Arb.string()With Kotest 5.6.0,
Codepoint.ascii()was changed to include a wider range of ascii chararacters, andCodepoint.printableAscii()was introduced with the historic range used byCodepoint.ascii().Arb.string()has been usingCodepoint.ascii()as it's default for generating chars for the string. This caused issues for some users, and we decided to revertArb.string()to the historic behavior by changing the default to the newCodepoint.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.1Maintenance release, published since 5.6.0 failed to upload for some targets.
Breaking changes (from 5.5.5 -> 5.6.x)
ConstantNow-related functions to a new module namedio.kotest:kotest-extensions-now(remember to add -jvm suffix for Maven)withConstantNowSee full changelog at https://kotest.io/docs/changelog.html
v5.6.0Breaking changes
ConstantNow-related functions to a new module namedio.kotest:kotest-extensions-now(remember to add -jvm suffix for Maven)withConstantNowSee full changelog at https://kotest.io/docs/changelog.html
v5.5.5v5.5.4Fixes issue 3277.
Contributors:
v5.5.3: 5.5.3Updated 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
ClassOrderernot being found. Please make sure that only JUnit 5.8+ is loadedv5.5.2Gradle test filter fixes, by @myuwono https://github.com/kotest/kotest/pull/3257
Tag inheritance configuration is now available on
AbstractProjectConfigv5.5.1: 5.5.1Fixed an issue where tests where being skipped when filtered out by the full spec name
v5.5.0Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR has been generated by Mend Renovate. View repository job log here.