Skip to content

chore(deps): Bump kotest from 6.2.2 to 6.2.3#852

Closed
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/gradle/kotest-6.2.3
Closed

chore(deps): Bump kotest from 6.2.2 to 6.2.3#852
dependabot[bot] wants to merge 1 commit into
developfrom
dependabot/gradle/kotest-6.2.3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 21, 2026

Copy link
Copy Markdown
Contributor

Bumps kotest from 6.2.2 to 6.2.3.
Updates io.kotest:kotest-runner-junit5 from 6.2.2 to 6.2.3

Release notes

Sourced from io.kotest:kotest-runner-junit5's releases.

v6.2.3

What's Changed

New Contributors

Full Changelog: kotest/kotest@6.2.2...v6.2.3

Commits

Updates io.kotest:kotest-assertions-core from 6.2.2 to 6.2.3

Release notes

Sourced from io.kotest:kotest-assertions-core's releases.

v6.2.3

What's Changed

New Contributors

Full Changelog: kotest/kotest@6.2.2...v6.2.3

Commits

Updates io.kotest:kotest-property from 6.2.2 to 6.2.3

Release notes

Sourced from io.kotest:kotest-property's releases.

v6.2.3

What's Changed

New Contributors

Full Changelog: kotest/kotest@6.2.2...v6.2.3

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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)

Bumps `kotest` from 6.2.2 to 6.2.3.

Updates `io.kotest:kotest-runner-junit5` from 6.2.2 to 6.2.3
- [Release notes](https://github.com/kotest/kotest/releases)
- [Commits](kotest/kotest@6.2.2...6.2.3)

Updates `io.kotest:kotest-assertions-core` from 6.2.2 to 6.2.3
- [Release notes](https://github.com/kotest/kotest/releases)
- [Commits](kotest/kotest@6.2.2...6.2.3)

Updates `io.kotest:kotest-property` from 6.2.2 to 6.2.3
- [Release notes](https://github.com/kotest/kotest/releases)
- [Commits](kotest/kotest@6.2.2...6.2.3)

---
updated-dependencies:
- dependency-name: io.kotest:kotest-runner-junit5
  dependency-version: 6.2.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: io.kotest:kotest-assertions-core
  dependency-version: 6.2.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
- dependency-name: io.kotest:kotest-property
  dependency-version: 6.2.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update java code labels Jul 21, 2026
@dependabot @github

dependabot Bot commented on behalf of github Jul 21, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@michalharakal
michalharakal deleted the dependabot/gradle/kotest-6.2.3 branch July 21, 2026 17:29
MacOS pushed a commit to MacOS/SKaiNET that referenced this pull request Jul 22, 2026
…akes

The single build-job ran `assemble allTests` in one ubuntu-latest job.
On a 7 GB runner the combined peak memory (Gradle JVM + Kotlin daemon +
per-target test forks + Node for JS/Wasm + native toolchain, all at
once) intermittently exceeded physical RAM. The runner was OOM-killed
and GitHub reported "The operation was canceled" after ~15 min with no
BUILD FAILED — the flaky ~20-minute red builds (seen on PRs SKaiNET-developers#850, SKaiNET-developers#852).

Changes:
- Split the test run into a matrix of three legs (jvm / js-wasm /
  native), each running one target family so no single job holds the
  whole footprint. Legs run in parallel, so wall-clock is the slowest
  leg instead of the sum.
- Run `assemble` as its own memory-light job, preserving the
  build/package guarantee for all targets.
- Add Gradle dependency/wrapper caching to each job (same pattern as
  docs.yml) so parallel legs don't cold-download the dependency graph.
- Capture the memory snapshot on `cancelled()` as well as `failure()`
  — an OOM-killed runner reports cancelled, not failed, so the existing
  diagnostic never fired on the runs that needed it.
- Keep an aggregate `build-job` gate with the same name so the existing
  required status check keeps working without re-pointing branch
  protection.

No production code changed; allTests passes locally.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant