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.

Sign up for GitHub

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

Jump to bottom

chore(deps): bump kotest.version from 5.5.5 to 5.6.2 #503

Merged
merged 1 commit into from
May 24, 2023
Merged

chore(deps): bump kotest.version from 5.5.5 to 5.6.2 #503

merged 1 commit into from
May 24, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 11, 2023 •
edited
Loading

Bumps kotest.version from 5.5.5 to 5.6.2.
Updates kotest-runner-junit4-jvm from 5.5.5 to 5.6.2

Release notes

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

v5.6.2

5.6.2 May 2023

Assertions

Property testing

  • Fixes a problem with property testing on Apple platforms #3506
  • Reverts behaviour of Arb.string() to only generate Strings of printable ascii characters
    • 5.6.0 changed it to include some control characters, see #3513 for details
  • Fix huge allocation for OffsetDateTime Arb without arguments by @​rescribet in kotest/kotest#3491
  • Fix Arb.map edgecases by @​myuwono in kotest/kotest#3496

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

... (truncated)

Commits

Updates kotest-runner-junit5-jvm from 5.5.5 to 5.6.2

Release notes

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

v5.6.2

5.6.2 May 2023

Assertions

Property testing

  • Fixes a problem with property testing on Apple platforms #3506
  • Reverts behaviour of Arb.string() to only generate Strings of printable ascii characters
    • 5.6.0 changed it to include some control characters, see #3513 for details
  • Fix huge allocation for OffsetDateTime Arb without arguments by @​rescribet in kotest/kotest#3491
  • Fix Arb.map edgecases by @​myuwono in kotest/kotest#3496

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

... (truncated)

Commits

Updates kotest-assertions-core-jvm from 5.5.5 to 5.6.2

Release notes

Sourced from kotest-assertions-core-jvm's releases.

v5.6.2

5.6.2 May 2023

Assertions

Property testing

  • Fixes a problem with property testing on Apple platforms #3506
  • Reverts behaviour of Arb.string() to only generate Strings of printable ascii characters
    • 5.6.0 changed it to include some control characters, see #3513 for details
  • Fix huge allocation for OffsetDateTime Arb without arguments by @​rescribet in kotest/kotest#3491
  • Fix Arb.map edgecases by @​myuwono in kotest/kotest#3496

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

... (truncated)

Commits

Updates kotest-property-jvm from 5.5.5 to 5.6.2

Release notes

Sourced from kotest-property-jvm's releases.

v5.6.2

5.6.2 May 2023

Assertions

Property testing

  • Fixes a problem with property testing on Apple platforms #3506
  • Reverts behaviour of Arb.string() to only generate Strings of printable ascii characters
    • 5.6.0 changed it to include some control characters, see #3513 for details
  • Fix huge allocation for OffsetDateTime Arb without arguments by @​rescribet in kotest/kotest#3491
  • Fix Arb.map edgecases by @​myuwono in kotest/kotest#3496

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

... (truncated)

Commits

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)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label May 11, 2023
@dependabot dependabot bot mentioned this pull request May 11, 2023
Closed
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

1 similar comment
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@oldratlee
Copy link
Member

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/maven/kotest.version-5.6.2 branch from b9b9a6f to c335b9d Compare May 16, 2023 08:38
@oldratlee
Copy link
Member

@dependabot recreate

@dependabot dependabot bot force-pushed the dependabot/maven/kotest.version-5.6.2 branch from c335b9d to b1aed9d Compare May 16, 2023 08:39
@oldratlee
Copy link
Member

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/maven/kotest.version-5.6.2 branch from b1aed9d to d18c8f9 Compare May 16, 2023 08:42
@oldratlee oldratlee force-pushed the master branch 3 times, most recently from 05ced9f to 9523d0d Compare May 16, 2023 11:38
@dependabot
chore(deps): bump kotest.version from 5.5.5 to 5.6.2
42027c0 
Dependabot couldn't find the original pull request head commit, d18c8f9.
@dependabot dependabot bot force-pushed the dependabot/maven/kotest.version-5.6.2 branch from d18c8f9 to 42027c0 Compare May 17, 2023 19:10
@oldratlee oldratlee merged commit b40fd9f into master May 24, 2023
@dependabot dependabot bot deleted the dependabot/maven/kotest.version-5.6.2 branch May 24, 2023 09:30
oldratlee pushed a commit that referenced this pull request May 24, 2023
@dependabot @oldratlee
chore(deps): upgrade dependencies/plugins 🛠️
461983e 
bump kotest.version from 5.5.5 to 5.6.2 (#503)
bump git-commit-id-maven-plugin from 5.0.0 to 6.0.0 (#506)
bump maven-source-plugin from 3.2.1 to 3.3.0 (#507)
bump maven-dependency-plugin from 3.5.0 to 3.6.0 (#508)
oldratlee pushed a commit that referenced this pull request Oct 10, 2023
@dependabot @oldratlee
chore(deps): upgrade dependencies/plugins 🛠️
071575b 
bump kotest.version from 5.5.5 to 5.6.2 (#503)
bump git-commit-id-maven-plugin from 5.0.0 to 6.0.0 (#506)
bump maven-source-plugin from 3.2.1 to 3.3.0 (#507)
bump maven-dependency-plugin from 3.5.0 to 3.6.0 (#508)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@CLAassistant @oldratlee