Extend plugin test coverage for newer framework versions #2382
wu-shengAnnotations
65 errors and 35 warnings
|
spring-kafka-2.3.x-scenario
Process completed with exit code 1.
|
|
spring-kafka-2.2.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
spring-kafka-2.2.x-scenario
The operation was canceled.
|
|
spring-scheduled-3.x-5.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
spring-scheduled-3.x-5.x-scenario
The operation was canceled.
|
|
vertx-web-3.6plus-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
vertx-web-3.6plus-scenario
The operation was canceled.
|
|
undertow-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
undertow-scenario
The operation was canceled.
|
|
vertx-web-3.54minus-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
vertx-web-3.54minus-scenario
The operation was canceled.
|
|
jsonrpc4j-1.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
jsonrpc4j-1.x-scenario
The operation was canceled.
|
|
spring-3.1.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
spring-3.1.x-scenario
The operation was canceled.
|
|
micronaut-http-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
micronaut-http-scenario
The operation was canceled.
|
|
mysql-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
mysql-scenario
The operation was canceled.
|
|
undertow-worker-thread-pool-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
undertow-worker-thread-pool-scenario
The operation was canceled.
|
|
thrift-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
thrift-scenario
The operation was canceled.
|
|
spring-kafka-1.3.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
spring-kafka-1.3.x-scenario
The operation was canceled.
|
|
vertx-eventbus-3.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
vertx-eventbus-3.x-scenario
The operation was canceled.
|
|
hikaricp-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
hikaricp-scenario
The operation was canceled.
|
|
mysql-9.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
mysql-9.x-scenario
The operation was canceled.
|
|
graphql-16plus-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
graphql-16plus-scenario
The operation was canceled.
|
|
spring-4.3.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
spring-4.3.x-scenario
The operation was canceled.
|
|
gateway-3.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
gateway-3.x-scenario
The operation was canceled.
|
|
graphql-12.x-15.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
graphql-12.x-15.x-scenario
The operation was canceled.
|
|
baidu-brpc-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
baidu-brpc-scenario
The operation was canceled.
|
|
dbcp-2.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
vertx-core-4.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
dbcp-2.x-scenario
The operation was canceled.
|
|
vertx-core-4.x-scenario
The operation was canceled.
|
|
neo4j-4.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
neo4j-4.x-scenario
The operation was canceled.
|
|
quartz-scheduler-2.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
quartz-scheduler-2.x-scenario
The operation was canceled.
|
|
gateway-3.x-filter-context-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
gateway-3.x-filter-context-scenario
The operation was canceled.
|
|
guava-eventbus-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
guava-eventbus-scenario
The operation was canceled.
|
|
webflux-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
webflux-scenario
The operation was canceled.
|
|
aerospike-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
aerospike-scenario
The operation was canceled.
|
|
tomcat-thread-pool-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
tomcat-thread-pool-scenario
The operation was canceled.
|
|
hbase-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
hbase-scenario
The operation was canceled.
|
|
kylin-jdbc-2.6.x-3.x-4.x-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
kylin-jdbc-2.6.x-3.x-4.x-scenario
The operation was canceled.
|
|
mariadb-scenario
The strategy configuration was canceled because "test.spring-kafka-2_3_x-scenar" failed
|
|
mariadb-scenario
The operation was canceled.
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
mysql-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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
test-plugin-workspace-aerospike-scenario
|
109 MB |
sha256:33e599b73e7cf204438ff614d6d8f195b94f0a5c5ed3ba2f9d9b56bb6eaba201
|
|
|
test-plugin-workspace-baidu-brpc-scenario
|
113 MB |
sha256:3f994900139ac27d88a1aa3cced2af99cd242143bc4df439cba45106e4e6dda6
|
|
|
test-plugin-workspace-dbcp-2.x-scenario
|
96.9 MB |
sha256:4ccabf44c48f266284900d7cf42cd13c7b56eb3cb0d095d7c651378cf918d2df
|
|
|
test-plugin-workspace-gateway-3.x-filter-context-scenario
|
81.8 MB |
sha256:787ce7aafd16067a23622f442f82879e2b5e1ed072f99957250a54e54beb7571
|
|
|
test-plugin-workspace-gateway-3.x-scenario
|
119 MB |
sha256:2658f6ade0137d0cee3f4b3be24c95952ce4ed29fab719c11befc60696077fe3
|
|
|
test-plugin-workspace-graphql-12.x-15.x-scenario
|
140 MB |
sha256:85fd3399edeb49266a0a72abe3f3be30d1582203a8775674f9605eb60f023161
|
|
|
test-plugin-workspace-graphql-16plus-scenario
|
151 MB |
sha256:542258d754b5f470609efbc309cc34c96c2b719396bfc37b5967dec3b286583c
|
|
|
test-plugin-workspace-guava-eventbus-scenario
|
102 MB |
sha256:2d9e39aaa016ee480ec07dd0ee37f0ff0d9b1f4701370224d33d96e9b976d82d
|
|
|
test-plugin-workspace-hbase-scenario
|
260 MB |
sha256:1ed7cb0f6c0c176bbae6c61770c101fe1e744b469cf062ec5d3f4ebaaba68a1b
|
|
|
test-plugin-workspace-hikaricp-scenario
|
95.9 MB |
sha256:03753b689268341c3506fea924988790844154d0ecbd6363d615340c9c72cd74
|
|
|
test-plugin-workspace-jsonrpc4j-1.x-scenario
|
1.11 KB |
sha256:3cff00d7c6466d5a7f3bd34b8facc2716f79939667568dbc77774d1a48042ebf
|
|
|
test-plugin-workspace-kylin-jdbc-2.6.x-3.x-4.x-scenario
|
43.6 MB |
sha256:0a75d8e4aff3c99fe9a8fefd9209c504a6f11bea5d8736c4a474b4b3d2b4c64c
|
|
|
test-plugin-workspace-mariadb-scenario
|
125 MB |
sha256:c38f12c9112d0a8fd753f8147efcc821a40ea9504eba5271a4b93ea82cf19c09
|
|
|
test-plugin-workspace-micronaut-http-scenario
|
71.8 MB |
sha256:a2cb60cf6e3d28bbc6de2e15ac1fbea5caa8fa7a8445634f461aeae882919635
|
|
|
test-plugin-workspace-mysql-9.x-scenario
|
114 MB |
sha256:58bd268e18cb862924184577a186d60eb9139093392ccd6c0b6863d69ca8b2fd
|
|
|
test-plugin-workspace-mysql-scenario
|
34.7 MB |
sha256:406f39358d267c182123d7ae6b2b06d517c7f966a3288cd1eef81c8820d17c39
|
|
|
test-plugin-workspace-neo4j-4.x-scenario
|
126 MB |
sha256:52949d59227927f1803e7967ac778bcddee693c330d7db2a5c4581cce2846c26
|
|
|
test-plugin-workspace-quartz-scheduler-2.x-scenario
|
190 MB |
sha256:3212dfcb91d684dee1990adc9b1541fd2d75950605fd327b7bc807d7d6602d86
|
|
|
test-plugin-workspace-shenyu-2.4.x-scenario
|
102 MB |
sha256:27bf11e381ca8c9c78f6cea19a3723d6d92bfc8085b82f4ffd28bfdeb3bcd35f
|
|
|
test-plugin-workspace-spring-3.1.x-scenario
|
63.5 MB |
sha256:f690866511acbe0fc88bb159b70302b99cf9b83feed4a8b660c70196a4e5fc29
|
|
|
test-plugin-workspace-spring-4.1.x-scenario
|
63.2 MB |
sha256:52ec40130dc73eaf956ce9173cdb7145ce76ac4bf0c261b015cc87100d69d5e8
|
|
|
test-plugin-workspace-spring-4.3.x-scenario
|
68.8 MB |
sha256:a0c2c7b8eb00e3d3490a795ccde3279f2f3f05d16efee580d61cade368334e56
|
|
|
test-plugin-workspace-spring-kafka-1.3.x-scenario
|
100 MB |
sha256:5ad73f5ec848f0f44630f640f74075ab4592134a727627834869b2653b427f96
|
|
|
test-plugin-workspace-spring-kafka-2.2.x-scenario
|
1.24 KB |
sha256:eeae797579eaa72bd3522330da91315b663f48576428af9b235783db357a1c5a
|
|
|
test-plugin-workspace-spring-kafka-2.3.x-scenario
|
97.5 MB |
sha256:0c4c949c352d9e652c614f95451081729b23c3bcaae2be0c239f6d518b3e58d5
|
|
|
test-plugin-workspace-spring-scheduled-3.x-5.x-scenario
|
23 MB |
sha256:d20064540306b964883f823e5eb3ab2911bc2165017b7bd8ad3d8524070a2d4f
|
|
|
test-plugin-workspace-thrift-scenario
|
49.5 MB |
sha256:4b88a45e229a165e3ffd44466a4f7c1cb98423c9bee9138116868f09b79e6033
|
|
|
test-plugin-workspace-tomcat-thread-pool-scenario
|
101 MB |
sha256:a6c2a71f5404f24a94ed9d1c5de06f72b67dcd1039cf38963bc8ca7076060118
|
|
|
test-plugin-workspace-undertow-scenario
|
22 MB |
sha256:78b6612352646a1c5355ba7a16ccdc4e344e7fb9e545d0e15d881f695267a610
|
|
|
test-plugin-workspace-undertow-worker-thread-pool-scenario
|
93.1 MB |
sha256:4733a7ea270b045066bbe9baccfaa200b48d8d90002b195208a8e17ba293f166
|
|
|
test-plugin-workspace-vertx-core-4.x-scenario
|
98 MB |
sha256:80bb15591894f66e2913950e318f8e3a90841fe5f7f95712bc7f446435ba0c1c
|
|
|
test-plugin-workspace-vertx-eventbus-3.x-scenario
|
91.9 MB |
sha256:928443f08dda7df06253fc836b2a70e0529a3496b28a0510755f8893320ee9d4
|
|
|
test-plugin-workspace-vertx-web-3.54minus-scenario
|
42.6 MB |
sha256:262edc0da7de0615e8d93d6f269d2d875247124bd374797dcf09faa71244c070
|
|
|
test-plugin-workspace-vertx-web-3.6plus-scenario
|
48.8 MB |
sha256:1eb00a46ca5cab8553468cf6ca5e289b701069f90468289502e4051f13e8a187
|
|
|
test-plugin-workspace-webflux-scenario
|
123 MB |
sha256:eb989f17f4ca5f899fceeeea21bdcf147a08f04bf2ed1ca95e17f6a3ee163814
|
|