Skip to content

chore(deps): update kotlin core dependencies #7281

chore(deps): update kotlin core dependencies

chore(deps): update kotlin core dependencies #7281

Triggered via pull request May 26, 2026 21:49
Status Failure
Total duration 2m 8s
Artifacts

diktat.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 5 warnings
diktat_check
Path does not exist: build/reports/diktat/diktat-merged.sarif
diktat_check
Gradle build failed: see console output for details
diktat_check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, github/codeql-action/upload-sarif@v3, gradle/actions/setup-gradle@v3.5.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
diktat_check
This job uses deprecated functionality from the 'gradle/gradle-build-action' action. Consult the Job Summary for more details.
diktat_check
No files were found with the provided path: **/build/reports/diktat. No artifacts will be uploaded.
diktat_check
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/
diktat_check
Failed to restore gradle-home-v1|Linux|diktat_check[80285d87e7e924763c21f7b49eaab733]-9dad06586a98ad1c9102737d37db165970b82182: Error: Cache service responded with 400