-
Notifications
You must be signed in to change notification settings - Fork 9
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
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/io.kotest-kotest-assertions-core-5.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
December 10, 2021 13:47
bc0971f
to
7491c61
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
December 19, 2021 08:06
7491c61
to
75b466c
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
January 17, 2022 11:22
75b466c
to
da25827
Compare
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
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
2 times, most recently
from
March 14, 2022 17:10
88e5aaa
to
8fb1c21
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
March 28, 2022 04:24
8fb1c21
to
3f7bba1
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
April 9, 2022 19:01
3f7bba1
to
34ac783
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
May 15, 2022 22:57
34ac783
to
125cdf7
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
2 times, most recently
from
June 25, 2022 09:04
f562ecf
to
f03e6fc
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
2 times, most recently
from
July 28, 2022 10:59
e683c61
to
9c55871
Compare
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
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
August 10, 2022 19:44
9c55871
to
4c92197
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
November 20, 2022 19:01
4c92197
to
6edc4cc
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
March 16, 2023 09:49
6edc4cc
to
fce2f8e
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
April 17, 2023 10:26
fce2f8e
to
2150ea9
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
May 28, 2023 11:19
2150ea9
to
cf7a900
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
July 20, 2023 18:38
cf7a900
to
92c9a14
Compare
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
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
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
3 times, most recently
from
September 5, 2023 21:42
c3dd600
to
1a50360
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
November 3, 2023 22:34
1a50360
to
44b75f5
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
February 2, 2024 10:52
44b75f5
to
010c5f8
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
March 11, 2024 06:57
010c5f8
to
874b933
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
May 9, 2024 21:16
874b933
to
12fd0a9
Compare
renovate
bot
force-pushed
the
renovate/io.kotest-kotest-assertions-core-5.x
branch
from
June 6, 2024 12:41
12fd0a9
to
e59696c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
4.6.3
->5.9.1
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
infix
variant ofshouldNotBeNull
that accepts a block by @sschuberth in https://github.com/kotest/kotest/pull/4060Framework
Property-testing
Arb.list<T?>
due to performance issues by @Kantis in https://github.com/kotest/kotest/pull/4023Docs
Build / CI/CD / Dependency updates
New Contributors
Full Changelog: kotest/kotest@v5.9.0...v5.9.1
v5.9.0
New Features
Breaking Changes
Requirements
What's Changed
collection.shouldContainAllInAnyOrder()
by @u-ways-e in https://github.com/kotest/kotest/pull/3995New Contributors
Full Changelog: kotest/kotest@v5.8.1...v5.9.0
v5.8.1
What's Changed
Long
assertions 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/3814intersect
matcher to ranges by @AlexCue987 in https://github.com/kotest/kotest/pull/3792shouldNotBePositive
andshouldNotBeNegative
matchers for BigDecimal by @pubiqq in https://github.com/kotest/kotest/pull/3818Iterable
inwithData
on root level by @obecker in https://github.com/kotest/kotest/pull/3831shouldBe expected
equivalent 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.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
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.1
Maintenance 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)withConstantNow
See full changelog at https://kotest.io/docs/changelog.html
v5.6.0
Breaking changes
ConstantNow
-related functions to a new module namedio.kotest:kotest-extensions-now
(remember to add -jvm suffix for Maven)withConstantNow
See full changelog at https://kotest.io/docs/changelog.html
v5.5.5
v5.5.4
Fixes 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
ClassOrderer
not being found. Please make sure that only JUnit 5.8+ is loadedv5.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.1Fixed an issue where tests where being skipped when filtered out by the full spec name
v5.5.0
v5.4.2
: 5.4.2v5.4.1
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.
This PR was generated by Mend Renovate. View the repository job log.