Fix httpclient-5.x plugin injecting sw8 headers into ClickHouse HTTP requests #2368
wu-shengplugins-test.3.yaml
on: pull_request
Build
11m 17s
Matrix: test
Annotations
45 errors and 57 warnings
|
shenyu-2.4.x-sofarpc-scenario
Process completed with exit code 1.
|
|
graphql-8.x-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
jdk-threadpool-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
micronaut-http-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
micronaut-http-scenario
The operation was canceled.
|
|
undertow-worker-thread-pool-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
undertow-worker-thread-pool-scenario
The operation was canceled.
|
|
vertx-eventbus-3.x-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
vertx-eventbus-3.x-scenario
The operation was canceled.
|
|
spring-async-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
spring-async-scenario
The operation was canceled.
|
|
vertx-web-3.54minus-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
vertx-web-3.54minus-scenario
The operation was canceled.
|
|
spring-kafka-2.2.x-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
spring-kafka-2.2.x-scenario
The operation was canceled.
|
|
kylin-jdbc-2.6.x-3.x-4.x-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
kylin-jdbc-2.6.x-3.x-4.x-scenario
The operation was canceled.
|
|
thrift-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
thrift-scenario
The operation was canceled.
|
|
neo4j-4.x-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
neo4j-4.x-scenario
The operation was canceled.
|
|
spring-scheduled-3.x-5.x-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
spring-scheduled-3.x-5.x-scenario
The operation was canceled.
|
|
mysql-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
mysql-scenario
The operation was canceled.
|
|
quartz-scheduler-2.x-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
quartz-scheduler-2.x-scenario
The operation was canceled.
|
|
xxl-job-2.2.0-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
xxl-job-2.2.0-scenario
The operation was canceled.
|
|
zookeeper-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
zookeeper-scenario
The operation was canceled.
|
|
graphql-12.x-15.x-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
graphql-12.x-15.x-scenario
The operation was canceled.
|
|
hikaricp-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
hikaricp-scenario
The operation was canceled.
|
|
hbase-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
hbase-scenario
The operation was canceled.
|
|
dbcp-2.x-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
dbcp-2.x-scenario
The operation was canceled.
|
|
mariadb-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
mariadb-scenario
The operation was canceled.
|
|
guava-eventbus-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
spring-3.1.x-scenario
The strategy configuration was canceled because "test.shenyu-2_4_x-sofarpc-scen" failed
|
|
guava-eventbus-scenario
The operation was canceled.
|
|
spring-3.1.x-scenario
The operation was canceled.
|
|
Build
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@v2, actions/setup-java@v2, actions/upload-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/
|
|
xxl-job-2.3.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
clickhouse-0.3.2.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
baidu-brpc-3.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
grpc-generic-call-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
retransform-class-tomcat-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
quasar-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
graphql-16plus-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
elasticjob-2.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
shenyu-2.4.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
gateway-3.x-filter-context-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
jdk-forkjoinpool-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
baidu-brpc-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
shenyu-2.4.x-grpc-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
shenyu-2.4.x-dubbo-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
druid-1.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
spring-4.1.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
clickhouse-0.3.1-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
graphql-9.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
solon-2.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
vertx-web-3.6plus-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
nats-2.14.x-2.16.5-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
vertx-core-4.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
retransform-class-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
aerospike-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
webflux-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
spring-kafka-1.3.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
jsonrpc4j-1.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
tomcat-thread-pool-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
gateway-3.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
spring-4.3.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
spring-kafka-2.3.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
undertow-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
shenyu-2.4.x-sofarpc-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
graphql-8.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
jdk-threadpool-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
micronaut-http-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
undertow-worker-thread-pool-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
vertx-eventbus-3.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
spring-async-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
vertx-web-3.54minus-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
spring-kafka-2.2.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
kylin-jdbc-2.6.x-3.x-4.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
thrift-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
neo4j-4.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
spring-scheduled-3.x-5.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
mysql-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
quartz-scheduler-2.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
xxl-job-2.2.0-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
zookeeper-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
graphql-12.x-15.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
hikaricp-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
hbase-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
dbcp-2.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
mariadb-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
guava-eventbus-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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/
|
|
spring-3.1.x-scenario
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@v2, actions/download-artifact@v4, actions/setup-java@v2, actions/upload-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 | |
|---|---|---|---|
|
skywalking-agent
|
44.3 MB |
sha256:a73e3c93fa4e7710ff25298cc51ecf83a208ea75c05b9aff31dc73ab666b7d0a
|
|
|
test-plugin-workspace-aerospike-scenario
|
145 MB |
sha256:a5afdad6b5d9f824183c146653dfe28235648b089ca8561a02fde57f20ac2748
|
|
|
test-plugin-workspace-baidu-brpc-3.x-scenario
|
52.1 MB |
sha256:0d0e176c9688d74d28dcf3240e4ce3c5bf68c8993abc1dcb957610ed16a6d7a2
|
|
|
test-plugin-workspace-baidu-brpc-scenario
|
170 MB |
sha256:a7c536502e4e36bd9d5689565de08ad456f604c35cfa856624b9adcc8aea5504
|
|
|
test-plugin-workspace-clickhouse-0.3.1-scenario
|
72.4 MB |
sha256:cdf3000ffb34f6f8948c14c9bc8eaffe31c792148f4fbf30b765a1cefcbdbad0
|
|
|
test-plugin-workspace-clickhouse-0.3.2.x-scenario
|
74 MB |
sha256:97c3eb9d8ee9a6ec654f6790b45d35afc753249b341f1ec43987f95b6e1b350f
|
|
|
test-plugin-workspace-dbcp-2.x-scenario
|
226 MB |
sha256:3ee712f182bc7244555c3cfcecbdcf2e2720543d237115009a9e320dcaf8497c
|
|
|
test-plugin-workspace-druid-1.x-scenario
|
108 MB |
sha256:bed2f8d8e04549cf1323bf08b294b06d1af6b4e0362bcb502e4f05e3dcc4dab0
|
|
|
test-plugin-workspace-elasticjob-2.x-scenario
|
97.8 MB |
sha256:e144f325043c27539156a13dce34ce18f9ee234b78fe53404c600b3557623596
|
|
|
test-plugin-workspace-gateway-3.x-filter-context-scenario
|
81.8 MB |
sha256:dd1f7f4e28b42e134d4475f3dd6839248da158f3277a6822db1c65648002f67a
|
|
|
test-plugin-workspace-gateway-3.x-scenario
|
157 MB |
sha256:358c2a7742a3d6a30555d1e80f93ad51f4a8a8fa055a974806125d4dda6dbf3a
|
|
|
test-plugin-workspace-graphql-12.x-15.x-scenario
|
69.9 MB |
sha256:6e7427183ba7dd880b5fc73d8f109ca3e2bc48b7ab73f1ea28d18a0c6e1d189a
|
|
|
test-plugin-workspace-graphql-16plus-scenario
|
74.7 MB |
sha256:6e863c6edd32b44b0ec89e94059bbf1baf22f0be862956683547c314f87792b0
|
|
|
test-plugin-workspace-graphql-8.x-scenario
|
34.1 MB |
sha256:54119abd7f85e99727a026c85631979b2d533855c9b5ceac0d2fefd3b0951f84
|
|
|
test-plugin-workspace-graphql-9.x-scenario
|
103 MB |
sha256:898a5820a56ea868386f95d8b795e73fe89b01da3d554859ab16218d8d01af0e
|
|
|
test-plugin-workspace-grpc-generic-call-scenario
|
50.4 MB |
sha256:ef852922a01a2aa5f88a0a396d07fed2003ad1ee62e3bbd8e73dcb24b533b047
|
|
|
test-plugin-workspace-guava-eventbus-scenario
|
137 MB |
sha256:8066e0fe6068e98100f6dbbc444f2ca511297aada81719d4c3b822d9e425393f
|
|
|
test-plugin-workspace-hbase-scenario
|
168 MB |
sha256:32ef439636d12a1b4f46551d8c7eccb57dbb006230f35c1d3133881321672a52
|
|
|
test-plugin-workspace-hikaricp-scenario
|
192 MB |
sha256:ca26707e9fbf33a1885f3fdac99db2620f4a7b00dc953c8ebde82a3633f6069d
|
|
|
test-plugin-workspace-jdk-forkjoinpool-scenario
|
77.9 MB |
sha256:8947fbd9f35024f90c753978724f8f02f149b4456cd7c9cd7b446ee6f270f9b7
|
|
|
test-plugin-workspace-jdk-threadpool-scenario
|
73 MB |
sha256:3fd61e3a4d35496e37181bbfbbbbbcf941aeb3194405f7c63ed60915cadbb449
|
|
|
test-plugin-workspace-jsonrpc4j-1.x-scenario
|
149 MB |
sha256:df750c56adcca83e0b7d0f4d8652b857078ddaffc47df56dca462da700256475
|
|
|
test-plugin-workspace-kylin-jdbc-2.6.x-3.x-4.x-scenario
|
43.6 MB |
sha256:c8608891132780b03a048747a94052b614acab2b07334522e1ba92980f4d20a2
|
|
|
test-plugin-workspace-mariadb-scenario
|
249 MB |
sha256:024cf67d87e10bb923b4bef8c04378ba360c3c48ed052aff48ba5c4c71f97918
|
|
|
test-plugin-workspace-micronaut-http-scenario
|
143 MB |
sha256:e6cb9cac431ef5328d6d6bc980ad89893ee588fac6ddbe6112e002c066fc8f2a
|
|
|
test-plugin-workspace-mysql-scenario
|
34.4 MB |
sha256:55ebd93f4a57dcd549332fe0f0e9a6846a46995ba1a51cd9c10fe48699cc681b
|
|
|
test-plugin-workspace-nats-2.14.x-2.16.5-scenario
|
104 MB |
sha256:3852be13a9e261c77904ed3260b695b65d448ffd4a009d12e1955c5f29ca47d8
|
|
|
test-plugin-workspace-neo4j-4.x-scenario
|
41.8 MB |
sha256:33661825a9abcfccaca541a28ec0efbff28a7bc550d338cf748d6b9e2e136b78
|
|
|
test-plugin-workspace-quartz-scheduler-2.x-scenario
|
117 MB |
sha256:8d66e17cefe8947b235ba6ab5ee6bd51fe44750fa6930bc5cca5695dbf145a80
|
|
|
test-plugin-workspace-quasar-scenario
|
38.9 MB |
sha256:d5e4c662313b8dacbd6d4d2c0b953d9525ea1f009b8cc686f6714073fe54068d
|
|
|
test-plugin-workspace-retransform-class-scenario
|
39.1 MB |
sha256:aaf6348b37a87071515a79b9c54404dd82b2a0ff7ee8be5edc7ac5c785111271
|
|
|
test-plugin-workspace-retransform-class-tomcat-scenario
|
10.6 MB |
sha256:ece5096b6c4c7d03de72ead0e7b7f072175c49032696a76c14e9ae8e9115b945
|
|
|
test-plugin-workspace-shenyu-2.4.x-dubbo-scenario
|
113 MB |
sha256:3d28c67f7b929a4af8c4ce5900d417adef1463d9f95e5b1d1c99346b26d6b320
|
|
|
test-plugin-workspace-shenyu-2.4.x-grpc-scenario
|
172 MB |
sha256:01a1d78d0b3061e9368790727f17dbee04449047d39b84e5564c673f1a13ef55
|
|
|
test-plugin-workspace-shenyu-2.4.x-scenario
|
102 MB |
sha256:8616749c9c8332917c39402a13f4348c18ba75d820a60f74ae05db230969a86f
|
|
|
test-plugin-workspace-shenyu-2.4.x-sofarpc-scenario
|
44.3 MB |
sha256:51b4567051cd17add8e476e1d549f1f085edaaa784e5bc9e2a2db032c787a896
|
|
|
test-plugin-workspace-solon-2.x-scenario
|
19.8 MB |
sha256:3993e30345d0d9fc56411a45b3e171e8652ca00d1f60f360c03cd6132b0d588c
|
|
|
test-plugin-workspace-spring-3.1.x-scenario
|
56.8 MB |
sha256:ad5215991357740e72d669d9a0836a45767b9ba6fa3b28d8947771f7648a1242
|
|
|
test-plugin-workspace-spring-4.1.x-scenario
|
63.2 MB |
sha256:79a46455e3f233b67cddda2e83e91dbb370617df3f1ef31dcb7614938fa2160e
|
|
|
test-plugin-workspace-spring-4.3.x-scenario
|
94.6 MB |
sha256:ca6e0bc46eb5f88e603b545b3ae099b677bd24ef362113becdbaa8f5da17f5be
|
|
|
test-plugin-workspace-spring-async-scenario
|
5.75 MB |
sha256:08d24b3495803d3cc4570c4602906f3bc9d1704518a1adfe908b0b35b0b8132f
|
|
|
test-plugin-workspace-spring-kafka-1.3.x-scenario
|
100 MB |
sha256:559096bfd24807c7fb7ac4ddcfbb0110b402a32a586fe099df00ed44a5c20de6
|
|
|
test-plugin-workspace-spring-kafka-2.2.x-scenario
|
40 MB |
sha256:647a42dc44c2fff7ca74826b1e3039adb3744d97ebb57aaddf3b2eb5ccc25612
|
|
|
test-plugin-workspace-spring-kafka-2.3.x-scenario
|
48.7 MB |
sha256:440767bf79e97852caea59ca1bc716351a7df019911bba8c3bfca0dc60dc4b05
|
|
|
test-plugin-workspace-spring-scheduled-3.x-5.x-scenario
|
57.8 MB |
sha256:ca6747ac0dec4a5aa86dcd1a9e78b2aa75a609f43b298514ef40e24f19ee8ed4
|
|
|
test-plugin-workspace-thrift-scenario
|
74.2 MB |
sha256:ca83a972f04e3e5ff76a4d0b0608e0e28723aee08edcdf3cf262c6feafa0498f
|
|
|
test-plugin-workspace-tomcat-thread-pool-scenario
|
168 MB |
sha256:0c4cbfc822e98aedc5df878c23c6c962d632f995a51eacb637e6ddb5e166693c
|
|
|
test-plugin-workspace-undertow-scenario
|
22 MB |
sha256:d3e10a84c824f1bb891138cc93cf75bfb9643bd88cab621d5958fe16f7262f74
|
|
|
test-plugin-workspace-undertow-worker-thread-pool-scenario
|
878 Bytes |
sha256:236acd2e735bfcb85f16b3b63860c86e6cbb3f5e7166711c9271ebf820533e04
|
|
|
test-plugin-workspace-vertx-core-4.x-scenario
|
98 MB |
sha256:08349643ce0f648861399202f313df74ece81d0989d7d0d62111744f9a3d3e09
|
|
|
test-plugin-workspace-vertx-eventbus-3.x-scenario
|
32.1 MB |
sha256:82881fd03409d6553a8297db90400ceb88f7cf111c02f8f9d9f0bcff3654ca20
|
|
|
test-plugin-workspace-vertx-web-3.54minus-scenario
|
34.4 MB |
sha256:eb8a9c34188591bc62f35495b1af8655dde6df2dee32b1926b0c9c9230f0920f
|
|
|
test-plugin-workspace-vertx-web-3.6plus-scenario
|
48.8 MB |
sha256:f8c8dabe331370b08a2972943934b23cfef79568f7a21ca72254729498063882
|
|
|
test-plugin-workspace-webflux-scenario
|
161 MB |
sha256:28a8eb51d124ad8bb4a507c69289c974f08b3f6340d2def72dbf24cfec8b4b9b
|
|
|
test-plugin-workspace-xxl-job-2.2.0-scenario
|
59.4 MB |
sha256:f40f36e447f6ee0e987184b32b1f439df0bd0d2fa93a96bfa2af6d3fe6494bc5
|
|
|
test-plugin-workspace-xxl-job-2.3.x-scenario
|
62 MB |
sha256:b2630822cba726a4578d8beecf582178bf68e5998f7a350ba56a09188166f10b
|
|
|
test-plugin-workspace-zookeeper-scenario
|
75.3 MB |
sha256:7eae6609bc44ff9577be3cb5e119d66e806f4bf00ec9585af74b4f0eab9dec24
|
|
|
test-tools
|
468 MB |
sha256:61ce49a82c3dcb255cb19e3482f6903c32abfa5045a5ae0133c59103696f2f70
|
|