Skip to content

docs: clarify upgrade from 3.x to 4.x #120

docs: clarify upgrade from 3.x to 4.x

docs: clarify upgrade from 3.x to 4.x #120

Triggered via pull request May 19, 2026 08:09
Status Failure
Total duration 9m 55s
Artifacts 18

java-ci.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 8 warnings
coverage_report
Process completed with exit code 1.
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, gradle/actions/setup-gradle@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/
unit_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. 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/
producer_only_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. 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/
redis_cluster_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. 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/
nats_integration_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. 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/
integration_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. 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/
reactive_integration_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. 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/
coverage_report
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. 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
coverage-integration
738 KB
sha256:505c850bd3bc7f32e7e0bfbbe021f0deb4dc030a6c791c0eee5d70d17994da0c
coverage-nats
315 KB
sha256:baea69653143c4485c1c2513ba8dd9ceab7ff83dff0dc255c7dee8c98e6b91ae
coverage-producer
314 KB
sha256:6b7768a694ae6c6aefed628c17b67791cbb1d2f24646b698ddb3e1409f3d2634
coverage-reactive
568 KB
sha256:50ce2e5ceaea92e010ba7e7e9889e1df14104428612d510b171c26b315bc0d5b
coverage-redis-cluster
524 KB
sha256:0924ddf8acddebd02a40dd9703c1429eda76215e7cb30d1418298c561ae34e44
coverage-report
1.36 MB
sha256:180e8213117e464338b56791e1739595e0dd4891b4469380025b4d5a1d2ab2c6
coverage-unit
513 KB
sha256:8f5b8071ecf19acf3edd25948f8e906bec10e0251f92e6388017d8b475d98843
integration-redis-server
734 Bytes
sha256:132432717ba41e08646f29784f5a0fb15bd7b44cb728f423c610833410f4028c
integration-test-results
29.7 KB
sha256:29c58817969ded322d31ef06905e2819715314b8faa0fe45468bfca36022120c
nats-server
853 Bytes
sha256:e701522f696e56398ca908261583992f84695ddf5efcc52e2d8bfc9c5ad631d9
nats-test-results
58.1 KB
sha256:a5cf35efbe63e09909c5357689d09c9c46943af8da297bea9287b3fd16066306
producer-redis-server
602 Bytes
sha256:5df41592f3ec0b526fb51e959f49587603f3a622e5da9a4ace15e82a84b61f58
producer-test-results
2.18 KB
sha256:3eae9c1d1f71a197309a3d0e0e35c6797b1603fb6f52b2d2ead58d2238b42a03
reactive-integration-test-results
28.2 KB
sha256:1c2847abd94324cdbd0837351c3d739e7a638e1004cd33cd44a5841ba73e6ed0
reactive-redis-server
733 Bytes
sha256:903aa35f1f4385153aa0f7d758dcece0d7adf2acdf85de463d5fc8196ab8d127
redis-cluster-test-results
6.08 KB
sha256:159e0800d5a89c3f9284f22ec1d0b56cd921e7f41465d5be0f2cc06d2c1a1fe6
redis-server-cluster
8.08 KB
sha256:fc0b0682a01b2ded71d60ae578ca5778fb7d006c4402ebaefcc0530b0806a59e
unit-test-results
46 KB
sha256:1d83862a250dd9aa689a87a2f2227b601be12996f445478800f881c9511e4711