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

Update kotest to v5.8.0 #6

Merged
merged 1 commit into from
Feb 1, 2024
Merged

Update kotest to v5.8.0 #6

merged 1 commit into from
Feb 1, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 1, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
io.kotest:kotest-property 5.6.0 -> 5.8.0 age adoption passing confidence
io.kotest:kotest-assertions-core 5.6.0 -> 5.8.0 age adoption passing confidence
io.kotest:kotest-runner-junit5 5.6.0 -> 5.8.0 age adoption passing confidence
io.kotest:kotest-bom 5.6.0 -> 5.8.0 age adoption passing confidence

Release Notes

kotest/kotest (io.kotest:kotest-property)

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


Configuration

📅 Schedule: Branch creation - "after 10am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about these updates 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 enabled auto-merge February 1, 2024 07:51
Copy link
Contributor Author

renovate bot commented Feb 1, 2024

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

@renovate renovate bot added this pull request to the merge queue Feb 1, 2024
Merged via the queue into main with commit 20beb6a Feb 1, 2024
8 checks passed
@renovate renovate bot deleted the renovate/kotest branch February 1, 2024 08:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants