26.1.2 support #149
Annotations
12 errors and 15 warnings
|
Java 21, Gradle wrapper on ubuntu-latest
Gradle build failed: see console output for details
|
|
Java 21, Gradle current on macos-latest
The strategy configuration was canceled because "build._21_wrapper_ubuntu-latest" failed
|
|
Java 21, Gradle current on macos-latest
The operation was canceled.
|
|
Java 21, Gradle current on ubuntu-latest
The strategy configuration was canceled because "build._21_wrapper_ubuntu-latest" failed
|
|
Java 21, Gradle current on ubuntu-latest
The operation was canceled.
|
|
Java 21, Gradle wrapper on windows-latest
The strategy configuration was canceled because "build._21_wrapper_ubuntu-latest" failed
|
|
Java 21, Gradle wrapper on windows-latest
The operation was canceled.
|
|
Java 21, Gradle wrapper on macos-latest
The strategy configuration was canceled because "build._21_wrapper_ubuntu-latest" failed
|
|
Java 21, Gradle wrapper on macos-latest
The operation was canceled.
|
|
Java 21, Gradle current on windows-latest
The strategy configuration was canceled because "build._21_wrapper_ubuntu-latest" failed
|
|
Java 21, Gradle current on windows-latest
The operation was canceled.
|
|
built
Process completed with exit code 1.
|
|
Java 21, Gradle wrapper on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-java@v2, gradle/gradle-build-action@v2. 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/
|
|
Java 21, Gradle wrapper on ubuntu-latest
Failed to restore v8-gradle|Linux|java ci with gradle-build[be7176116066e623ccac4055babc382d]-f7f1abb0019c9532af072df074ceb24980bdb039: Error: Cache service responded with 400
|
|
Java 21, Gradle current on macos-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-java@v2, gradle/gradle-build-action@v2. 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/
|
|
Java 21, Gradle current on macos-latest
Restore Gradle distribution 9.4.1 failed: Error: Cache service responded with 400
|
|
Java 21, Gradle current on macos-latest
Failed to restore v8-gradle|macOS|java ci with gradle-build[3f931a500668143a0f8404ec485f7d66]-f7f1abb0019c9532af072df074ceb24980bdb039: Error: Cache service responded with 400
|
|
Java 21, Gradle current on ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-java@v2, gradle/gradle-build-action@v2. 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/
|
|
Java 21, Gradle current on ubuntu-latest
Restore Gradle distribution 9.4.1 failed: Error: Cache service responded with 400
|
|
Java 21, Gradle current on ubuntu-latest
Failed to restore v8-gradle|Linux|java ci with gradle-build[4654dbf47e6778faf68a0ddab3de0fff]-f7f1abb0019c9532af072df074ceb24980bdb039: Error: Cache service responded with 400
|
|
Java 21, Gradle wrapper on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-java@v2, gradle/gradle-build-action@v2. 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/
|
|
Java 21, Gradle wrapper on windows-latest
Failed to restore v8-gradle|Windows|java ci with gradle-build[301a289759785fe11a81bfa5a22d89e5]-f7f1abb0019c9532af072df074ceb24980bdb039: Error: Cache service responded with 400
|
|
Java 21, Gradle wrapper on macos-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-java@v2, gradle/gradle-build-action@v2. 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/
|
|
Java 21, Gradle wrapper on macos-latest
Failed to restore v8-gradle|macOS|java ci with gradle-build[8432ec2d73d6033a6fa4a732714e3604]-f7f1abb0019c9532af072df074ceb24980bdb039: Error: Cache service responded with 400
|
|
Java 21, Gradle current on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-java@v2, gradle/gradle-build-action@v2. 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/
|
|
Java 21, Gradle current on windows-latest
Restore Gradle distribution 9.4.1 failed: Error: Cache service responded with 400
|
|
Java 21, Gradle current on windows-latest
Failed to restore v8-gradle|Windows|java ci with gradle-build[dab83fcce13f8960324b1b60f60fe537]-f7f1abb0019c9532af072df074ceb24980bdb039: Error: Cache service responded with 400
|