fix: restore Jackson 2.x property order in RqueueRedisSerializer to prevent stale processing-queue entries after 3.x → 4.x upgrade #116
sonus21java-ci.yaml
on: pull_request
build
1m 26s
unit_test
2m 6s
producer_only_test
1m 53s
integration_test
5m 37s
redis_cluster_test
3m 28s
reactive_integration_test
6m 11s
nats_integration_test
5m 25s
coverage_report
58s
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/
|
|
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/
|
|
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/
|
|
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:cddd4e75c9654f3fb56f32c1ccc328c0a509c6688f8d3b4d31fa21d6ab615713
|
|
|
coverage-nats
|
315 KB |
sha256:533b741fb2fd80d3f5060415e4d65e40d6d168955bb04ad5b5a8ed0299534ff6
|
|
|
coverage-producer
|
314 KB |
sha256:a17b2cc670333c59c47d41213be1bd8fa3ed4385add2b05f28ba5b55ec8857b2
|
|
|
coverage-reactive
|
568 KB |
sha256:2c93ad9626780d69056ba5f0c0f972005375b52b91a2c1b54ed98be311aa3a3d
|
|
|
coverage-redis-cluster
|
514 KB |
sha256:e2658206d32cf98823d57ee9d92c16c83d639c7c4c987690799d6b7868dc617a
|
|
|
coverage-report
|
1.36 MB |
sha256:568d827985e3bcc8af49e649d0501a01016aa3f734edcd611909a0dcf258c03b
|
|
|
coverage-unit
|
513 KB |
sha256:2d8b783b99d830d1725f27df124a1094c9e258064bf39557c37666693fcee4a8
|
|
|
integration-redis-server
|
731 Bytes |
sha256:c0c05608bf6d61732609874825fe772192e7a207d0ebf7ab95fc31b4e8df1fcb
|
|
|
integration-test-results
|
29.7 KB |
sha256:4af29cc0dbaa5c0619a2255f0e7e15240aa31bb620d0cd61aa68592b76ea8996
|
|
|
nats-server
|
850 Bytes |
sha256:c84d7532106937b4f3d5a7b3bbfd6d4be77c3fa3ba595c1fcbb7dbf441067949
|
|
|
nats-test-results
|
57.3 KB |
sha256:bd63020af6e1dc77b78257f5d6814dbb5fc50267a743ba95673184b31420a876
|
|
|
producer-redis-server
|
603 Bytes |
sha256:fbd88915ff3573bc865b1b93bbdf5d31501058ac16e972048bcc09911c289b73
|
|
|
producer-test-results
|
2.19 KB |
sha256:67c114e5481e1c853dc3faeb213ed54b0195a5a06585980f25179d4393e31d34
|
|
|
reactive-integration-test-results
|
28.2 KB |
sha256:247fdbab209d95487d1445c1e7e6fe742bc93799264981f25fb86cfe56c22afd
|
|
|
reactive-redis-server
|
733 Bytes |
sha256:5cce44328ed04bda7f9ea1758e4cde5a895a9c4a2b189b78d825777b04e567fc
|
|
|
redis-cluster-test-results
|
6.09 KB |
sha256:ca40040bff5eac8b9ac9ab04f126907b1239c967755afdc20a78cf861ba1bc9d
|
|
|
redis-server-cluster
|
8.08 KB |
sha256:10285666e859efd86c24e02a3b6224fd06bbf31112ed761971eedbcf38503d35
|
|
|
unit-test-results
|
46.1 KB |
sha256:4cf1fa52a9e363919f808ab1397812bcab0f446a8fd3b230e5438d8f686b5585
|
|