Skip to content

chore(deps): update kotlin core dependencies to v2 #2555

chore(deps): update kotlin core dependencies to v2

chore(deps): update kotlin core dependencies to v2 #2555

Triggered via pull request March 16, 2026 09:40
Status Failure
Total duration 2m 40s
Artifacts 3

build_and_test.yml

on: pull_request
Matrix: Build and test
Matrix: Publish JUnit test results
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 18 warnings
Build and test (macos-latest)
No test report files were found
Build and test (macos-latest)
Gradle build failed: see console output for details
Build and test (ubuntu-latest)
No test report files were found
Build and test (ubuntu-latest)
Gradle build failed: see console output for details
Build and test (windows-latest)
No test report files were found
Build and test (windows-latest)
Gradle build failed: see console output for details
Publish JUnit test results (ubuntu-latest)
Unable to download artifact(s): Artifact not found for name: xml-test-reports-Linux Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
Publish JUnit test results (macos-latest)
Unable to download artifact(s): Artifact not found for name: xml-test-reports-macOS Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
Publish JUnit test results (windows-latest)
Unable to download artifact(s): Artifact not found for name: xml-test-reports-Windows Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md
Build and test (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, dorny/test-reporter@v1, gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build and test (macos-latest)
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
Build and test (macos-latest)
No files were found with the provided path: **/build/test-results/*/TEST-*.xml. No artifacts will be uploaded.
Build and test (macos-latest)
No file matches path **/build/test-results/*/TEST-*.xml
Build and test (macos-latest)
Failed to restore gradle-home-v1|macOS|build_and_test_with_code_coverage[94b0c994a2f9f0083256b240c3127624]-d76a314d4f4435bcf22f014664ae97d410d5debd: Error: Cache service responded with 400
Build and test (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, dorny/test-reporter@v1, gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build and test (ubuntu-latest)
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
Build and test (ubuntu-latest)
No files were found with the provided path: **/build/test-results/*/TEST-*.xml. No artifacts will be uploaded.
Build and test (ubuntu-latest)
No file matches path **/build/test-results/*/TEST-*.xml
Build and test (ubuntu-latest)
Failed to restore gradle-home-v1|Linux|build_and_test_with_code_coverage[d66a50bda5d79d0ce2b14f3c9b2182aa]-d76a314d4f4435bcf22f014664ae97d410d5debd: Error: Cache service responded with 400
Build and test (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, dorny/test-reporter@v1, gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build and test (windows-latest)
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
Build and test (windows-latest)
No files were found with the provided path: **/build/test-results/*/TEST-*.xml. No artifacts will be uploaded.
Build and test (windows-latest)
No file matches path **/build/test-results/*/TEST-*.xml
Build and test (windows-latest)
Failed to restore gradle-home-v1|Windows|build_and_test_with_code_coverage[dd97fabbdf7d1be5898e7f8512bff3bf]-d76a314d4f4435bcf22f014664ae97d410d5debd: Error: Cache service responded with 400
Publish JUnit test results (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Publish JUnit test results (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Publish JUnit test results (windows-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
gradle-reports-macos-latest Expired
38.4 KB
sha256:d7226707c2637a6e1e82406b22132a21cffeb7feff8b8ad9efa3c6b60b9079d0
gradle-reports-ubuntu-latest Expired
38.4 KB
sha256:495fc06996acf0e3cc9150c511261f42329c05ddeaa524e543bce51dad6cc21a
gradle-reports-windows-latest Expired
38.4 KB
sha256:271d9d65395819a85839e5f6ab7dc1e44e422057e3baf59089934c423b0ed667