Skip to content

Update to Gradle 8 with higher JDK Support #657

Update to Gradle 8 with higher JDK Support

Update to Gradle 8 with higher JDK Support #657

Triggered via pull request March 19, 2026 09:26
@xerufxeruf
synchronize #439
chore/gradle7
Status Failure
Total duration 4m 40s
Artifacts 9

gradle.yml

on: pull_request
Matrix: build
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 9 warnings
build (macos-latest, 17)
Process completed with exit code 1.
build (ubuntu-latest, 21)
Process completed with exit code 1.
build (ubuntu-latest, 11)
Process completed with exit code 1.
build (ubuntu-latest, 17)
Process completed with exit code 1.
build (windows-latest, 17)
Process completed with exit code 1.
build (macos-latest, 11)
Process completed with exit code 1.
build (windows-latest, 21)
Process completed with exit code 1.
build (windows-latest, 11)
Process completed with exit code 1.
build (macos-latest, 21)
Process completed with exit code 1.
build (macos-latest, 17)
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, gradle/actions/setup-gradle@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/
build (ubuntu-latest, 21)
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, gradle/actions/setup-gradle@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/
build (ubuntu-latest, 11)
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, gradle/actions/setup-gradle@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/
build (ubuntu-latest, 17)
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, gradle/actions/setup-gradle@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/
build (windows-latest, 17)
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, gradle/actions/setup-gradle@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/
build (macos-latest, 11)
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, gradle/actions/setup-gradle@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/
build (windows-latest, 21)
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, gradle/actions/setup-gradle@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/
build (windows-latest, 11)
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, gradle/actions/setup-gradle@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/
build (macos-latest, 21)
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, gradle/actions/setup-gradle@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
test-reports-macos-latest-jdk11-c68e28a44ae729ddb6c3557cc15040ed028d8dc0
3.66 MB
sha256:517ba99097b52146f32e8cd2c46de1919b74f7a9af52f18ae947f31a89c4ca9b
test-reports-macos-latest-jdk17-c68e28a44ae729ddb6c3557cc15040ed028d8dc0
107 KB
sha256:76d9c6aea1282c357bd2911f787195f56845cfdf63daba25609c6a34fb12e574
test-reports-macos-latest-jdk21-c68e28a44ae729ddb6c3557cc15040ed028d8dc0
3.63 MB
sha256:7117744d60a5db6c1fc599aef4aa1c69867647820377d5a8b90b8fbdea3a7a06
test-reports-ubuntu-latest-jdk11-c68e28a44ae729ddb6c3557cc15040ed028d8dc0
3.68 MB
sha256:b7080b22d469e4f78966bc3543638f1f712c617c9645bb75c39c8f8202bd0500
test-reports-ubuntu-latest-jdk17-c68e28a44ae729ddb6c3557cc15040ed028d8dc0
3.65 MB
sha256:7a14d24446aff48dff1b803f2edde3ec799b491d678e47faf96803da3bf8de24
test-reports-ubuntu-latest-jdk21-c68e28a44ae729ddb6c3557cc15040ed028d8dc0
3.65 MB
sha256:5053811e0ccb1c205f03d622290e4614d199466ad5340056ec50e0326ea78168
test-reports-windows-latest-jdk11-c68e28a44ae729ddb6c3557cc15040ed028d8dc0
3.68 MB
sha256:1ad4aa35c8ba6a7ff190edf9a212cf7181035cdb77c353c0f7ce78dd32dae974
test-reports-windows-latest-jdk17-c68e28a44ae729ddb6c3557cc15040ed028d8dc0
3.61 MB
sha256:131f31894820c83259d36048729dc60bb51c47ab1c2a8c6ed202fa7efa9acff7
test-reports-windows-latest-jdk21-c68e28a44ae729ddb6c3557cc15040ed028d8dc0
3.65 MB
sha256:4f2595450a62d4dd81b33d933564c138f081ca1d3897ae1d7e0a1a21d5e4fda5