Update Khepri from 0.17.6 to 0.17.7 #7336
dumbbelltest-make.yaml
on: pull_request
Matrix: Build and Xref
Matrix: Test mixed clusters
Matrix: Test
Matrix: Type check
Annotations
3 errors and 184 warnings
|
Test (28, 1.18) / Test rabbit (parallel-ct-set-1) / rabbit (parallel-ct-set-1)
{rabbit_db_topic_exchange_SUITE,end_per_testcase,{'EXIT',{{exception,undef,[{rabbit_db_topic_exchange,clear,[],[]}]},[{erpc,call,5,[{file,"erpc.erl"},{line,1380}]},{rabbit_db_topic_exchange_SUITE,end_per_testcase,2,[{file,"deps/rabbit/test/rabbit_db_topic_exchange_SUITE.erl"},{line,84}]},{test_server,do_end_per_testcase,4,[{file,"test_server.erl"},{line,1640}]},{test_server,run_test_case_eval1,6,[{file,"test_server.erl"},{line,1348}]},{test_server,run_test_case_eval,9,[{file,"test_server.erl"},{line,1237}]}]}}}
|
|
Test mixed clusters (28, 1.18) / Test rabbit (parallel-ct-set-1) / rabbit (parallel-ct-set-1)
{rabbit_db_topic_exchange_SUITE,end_per_testcase,{'EXIT',{{exception,undef,[{rabbit_db_topic_exchange,clear,[],[]}]},[{erpc,call,5,[{file,"erpc.erl"},{line,1380}]},{rabbit_db_topic_exchange_SUITE,end_per_testcase,2,[{file,"deps/rabbit/test/rabbit_db_topic_exchange_SUITE.erl"},{line,84}]},{test_server,do_end_per_testcase,4,[{file,"test_server.erl"},{line,1640}]},{test_server,run_test_case_eval1,6,[{file,"test_server.erl"},{line,1348}]},{test_server,run_test_case_eval,9,[{file,"test_server.erl"},{line,1237}]}]}}}
|
|
Test mixed clusters (28, 1.18) / Test rabbitmq_mqtt / rabbitmq_mqtt (parallel-ct-set-1)
{error,{{assertEqual,[{module,rabbit_ct_broker_helpers},{line,1174},{expression,"CrashesCount"},{expected,0},{value,1}]},[{rabbit_ct_broker_helpers,find_crashes_in_logs,2,[{file,"deps/rabbitmq_mqtt/src/rabbit_ct_broker_helpers.erl"},{line,1174}]},{rabbit_ct_broker_helpers,stop_rabbitmq_nodes,1,[{file,"src/rabbit_ct_broker_helpers.erl"},{line,1123}]},{rabbit_ct_helpers,run_steps,2,[{file,"src/rabbit_ct_helpers.erl"},{line,126}]},{test_server,ts_tc,3,[{file,"test_server.erl"},{line,1796}]},{test_server,run_test_case_eval1,6,[{file,"test_server.erl"},{line,1393}]},{test_server,run_test_case_eval,9,[{file,"test_server.erl"},{line,1237}]}]}}
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_prelaunch) / rabbitmq_prelaunch (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_prelaunch) / rabbitmq_prelaunch (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_stream_common) / rabbitmq_stream_common (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_stream_common) / rabbitmq_stream_common (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_stream_common) / rabbitmq_stream_common (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (amqp10_common) / amqp10_common (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (amqp10_common) / amqp10_common (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (amqp10_common) / amqp10_common (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (amqp_client) / amqp_client (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_prelaunch) / rabbitmq_prelaunch (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbit_common) / rabbit_common (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbit_common) / rabbit_common (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (trust_store_http) / trust_store_http (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_ct_client_helpers) / rabbitmq_ct_client_helpers (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbit_common) / rabbit_common (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_amqp_client) / rabbitmq_amqp_client (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (amqp10_client) / amqp10_client (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_peer_discovery_k8s) / rabbitmq_peer_discovery_k8s (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_auth_mechanism_ssl) / rabbitmq_auth_mechanism_ssl (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_jms_topic_exchange) / rabbitmq_jms_topic_exchange (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_web_dispatch) / rabbitmq_web_dispatch (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_federation_common) / rabbitmq_federation_common (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (oauth2_client) / oauth2_client (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_sharding) / rabbitmq_sharding (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_peer_discovery_k8s) / rabbitmq_peer_discovery_k8s (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_federation_common) / rabbitmq_federation_common (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_jms_topic_exchange) / rabbitmq_jms_topic_exchange (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (oauth2_client) / oauth2_client (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbitmq_peer_discovery_aws (partially) / rabbitmq_peer_discovery_aws (ct-config_schema ct-unit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_sharding) / rabbitmq_sharding (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_aws) / rabbitmq_aws (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_web_dispatch) / rabbitmq_web_dispatch (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbitmq_peer_discovery_aws (partially) / rabbitmq_peer_discovery_aws (ct-config_schema ct-unit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_recent_history_exchange) / rabbitmq_recent_history_exchange (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_auth_mechanism_ssl) / rabbitmq_auth_mechanism_ssl (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_event_exchange) / rabbitmq_event_exchange (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_stream_management) / rabbitmq_stream_management (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_recent_history_exchange) / rabbitmq_recent_history_exchange (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_aws) / rabbitmq_aws (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (ct-metadata_store_clustering) / rabbit (ct-metadata_store_clustering)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_auth_backend_http) / rabbitmq_auth_backend_http (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_federation_management) / rabbitmq_federation_management (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_federation_prometheus) / rabbitmq_federation_prometheus (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_auth_backend_http) / rabbitmq_auth_backend_http (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_tracing) / rabbitmq_tracing (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_amqp_client) / rabbitmq_amqp_client (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_federation_management) / rabbitmq_federation_management (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_amqp_client) / rabbitmq_amqp_client (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_recent_history_exchange) / rabbitmq_recent_history_exchange (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_event_exchange) / rabbitmq_event_exchange (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_jms_topic_exchange) / rabbitmq_jms_topic_exchange (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_tracing) / rabbitmq_tracing (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_federation_prometheus) / rabbitmq_federation_prometheus (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_auth_backend_ldap) / rabbitmq_auth_backend_ldap (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_stream) / rabbitmq_stream (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_peer_discovery_consul) / rabbitmq_peer_discovery_consul (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_shovel_prometheus) / rabbitmq_shovel_prometheus (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_random_exchange) / rabbitmq_random_exchange (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_peer_discovery_common) / rabbitmq_peer_discovery_common (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_peer_discovery_common) / rabbitmq_peer_discovery_common (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_peer_discovery_aws) / rabbitmq_peer_discovery_aws (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_peer_discovery_k8s) / rabbitmq_peer_discovery_k8s (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (ct-peer_discovery_classic_config) / rabbit (ct-peer_discovery_classic_config)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_sharding) / rabbitmq_sharding (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_auth_backend_cache) / rabbitmq_auth_backend_cache (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_management_agent) / rabbitmq_management_agent (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_consistent_hash_exchange) / rabbitmq_consistent_hash_exchange (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_queue_federation) / rabbitmq_queue_federation (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_federation_common) / rabbitmq_federation_common (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_shovel_prometheus) / rabbitmq_shovel_prometheus (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_exchange_federation) / rabbitmq_exchange_federation (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_web_stomp) / rabbitmq_web_stomp (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_auth_mechanism_ssl) / rabbitmq_auth_mechanism_ssl (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_web_stomp) / rabbitmq_web_stomp (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_ct_helpers) / rabbitmq_ct_helpers (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_web_mqtt_examples) / rabbitmq_web_mqtt_examples (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_management_agent) / rabbitmq_management_agent (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_web_stomp) / rabbitmq_web_stomp (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_auth_backend_http) / rabbitmq_auth_backend_http (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_web_dispatch) / rabbitmq_web_dispatch (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_peer_discovery_common) / rabbitmq_peer_discovery_common (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_auth_backend_ldap) / rabbitmq_auth_backend_ldap (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_queue_federation) / rabbitmq_queue_federation (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_management_agent) / rabbitmq_management_agent (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_aws) / rabbitmq_aws (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_aws) / rabbitmq_aws (dialyze)
missing specification for function from_ucs4be/2
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_aws) / rabbitmq_aws (dialyze)
missing specification for function from_ucs4be/1
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_aws) / rabbitmq_aws (dialyze)
missing specification for function to_ucs4be/1
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_aws) / rabbitmq_aws (dialyze)
missing specification for function is_visible_ascii/1
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_aws) / rabbitmq_aws (dialyze)
missing specification for function is_visible_latin1/1
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_aws) / rabbitmq_aws (dialyze)
missing specification for function is_iso646_basic/1
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_aws) / rabbitmq_aws (dialyze)
missing specification for function is_ascii/1
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_aws) / rabbitmq_aws (dialyze)
missing specification for function is_latin1/1
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_aws) / rabbitmq_aws (dialyze)
missing specification for function is_bmpchar/1
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_aws) / rabbitmq_aws (dialyze)
missing specification for function is_unicode/1
|
|
Test (28, 1.18) / Test plugins (amqp_client) / amqp_client (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (oauth2_client) / oauth2_client (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_web_stomp_examples) / rabbitmq_web_stomp_examples (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_event_exchange) / rabbitmq_event_exchange (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_consistent_hash_exchange) / rabbitmq_consistent_hash_exchange (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_shovel) / rabbitmq_shovel (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_shovel_management) / rabbitmq_shovel_management (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_auth_backend_oauth2) / rabbitmq_auth_backend_oauth2 (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_prometheus) / rabbitmq_prometheus (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_trust_store) / rabbitmq_trust_store (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_shovel_management) / rabbitmq_shovel_management (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (amqp_client) / amqp_client (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_exchange_federation) / rabbitmq_exchange_federation (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_federation_prometheus) / rabbitmq_federation_prometheus (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_top) / rabbitmq_top (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_auth_backend_ldap) / rabbitmq_auth_backend_ldap (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_stream_management) / rabbitmq_stream_management (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_consistent_hash_exchange) / rabbitmq_consistent_hash_exchange (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Build and Xref (28, 1.18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Build and Xref (28, 1.18)
the callback gen_server:format_status(_,_) is deprecated; use format_status/1 instead
|
|
Test (28, 1.18) / Test rabbit (ct-rabbit_fifo_prop) / rabbit (ct-rabbit_fifo_prop)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_queue_federation) / rabbitmq_queue_federation (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbit) / rabbit (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_tracing) / rabbitmq_tracing (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Build and Xref (26, 1.18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_federation_management) / rabbitmq_federation_management (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_management) / rabbitmq_management (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (ct-peer_discovery_classic_config) / rabbit (ct-peer_discovery_classic_config)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (ct-rabbit_fifo_prop) / rabbit (ct-rabbit_fifo_prop)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_exchange_federation) / rabbitmq_exchange_federation (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_shovel_prometheus) / rabbitmq_shovel_prometheus (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Build and Xref (27, 1.18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Build and Xref (27, 1.18)
the callback gen_server:format_status(_,_) is deprecated; use format_status/1 instead
|
|
Test (28, 1.18) / Test plugins (rabbitmq_trust_store) / rabbitmq_trust_store (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Type check (28, 1.18) / Type check plugins (rabbitmq_shovel_management) / rabbitmq_shovel_management (dialyze)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_trust_store) / rabbitmq_trust_store (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_auth_backend_oauth2) / rabbitmq_auth_backend_oauth2 (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_auth_backend_oauth2) / rabbitmq_auth_backend_oauth2 (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_peer_discovery_etcd) / rabbitmq_peer_discovery_etcd (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_stream_management) / rabbitmq_stream_management (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_peer_discovery_etcd) / rabbitmq_peer_discovery_etcd (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_auth_backend_cache) / rabbitmq_auth_backend_cache (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_prometheus) / rabbitmq_prometheus (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_prometheus) / rabbitmq_prometheus (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_auth_backend_cache) / rabbitmq_auth_backend_cache (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (amqp10_client) / amqp10_client (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (amqp10_client) / amqp10_client (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (parallel-ct-set-3) / rabbit (parallel-ct-set-3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (parallel-ct-set-5) / rabbit (parallel-ct-set-5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (eunit ct-dead_lettering) / rabbit (eunit ct-dead_lettering)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_peer_discovery_consul) / rabbitmq_peer_discovery_consul (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (parallel-ct-set-5) / rabbit (parallel-ct-set-5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (eunit ct-dead_lettering) / rabbit (eunit ct-dead_lettering)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_peer_discovery_consul) / rabbitmq_peer_discovery_consul (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_stream) / rabbitmq_stream (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (parallel-ct-set-4) / rabbit (parallel-ct-set-4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (parallel-ct-set-3) / rabbit (parallel-ct-set-3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_stomp) / rabbitmq_stomp (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (ct-amqp_client) / rabbit (ct-amqp_client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (parallel-ct-set-4) / rabbit (parallel-ct-set-4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (parallel-ct-set-2) / rabbit (parallel-ct-set-2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_stomp) / rabbitmq_stomp (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (parallel-ct-set-2) / rabbit (parallel-ct-set-2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (ct-amqp_client) / rabbit (ct-amqp_client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (ct-quorum_queue) / rabbit (ct-quorum_queue)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (ct-feature_flags) / rabbit (ct-feature_flags)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (ct-rabbit_stream_queue) / rabbit (ct-rabbit_stream_queue)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (ct-clustering_management) / rabbit (ct-clustering_management)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_management) / rabbitmq_management (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbitmq_mqtt / rabbitmq_mqtt (parallel-ct-set-1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (ct-rabbit_stream_queue) / rabbit (ct-rabbit_stream_queue)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (ct-feature_flags) / rabbit (ct-feature_flags)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (ct-quorum_queue) / rabbit (ct-quorum_queue)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (ct-metadata_store_clustering) / rabbit (ct-metadata_store_clustering)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (parallel-ct-set-1) / rabbit (parallel-ct-set-1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (ct-clustering_management) / rabbit (ct-clustering_management)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_cli) / rabbitmq_cli (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_cli) / rabbitmq_cli (tests)
the callback gen_server:format_status(_,_) is deprecated; use format_status/1 instead
|
|
Test (28, 1.18) / Test plugins (rabbitmq_cli) / rabbitmq_cli (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_cli) / rabbitmq_cli (tests)
the callback gen_server:format_status(_,_) is deprecated; use format_status/1 instead
|
|
Test mixed clusters (28, 1.18) / Test rabbit (parallel-ct-set-1) / rabbit (parallel-ct-set-1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_shovel) / rabbitmq_shovel (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test rabbit (ct-clustering_recovery) / rabbit (ct-clustering_recovery)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbit (ct-clustering_recovery) / rabbit (ct-clustering_recovery)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test (28, 1.18) / Test plugins (rabbitmq_web_mqtt) / rabbitmq_web_mqtt (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_management) / rabbitmq_management (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_web_mqtt) / rabbitmq_web_mqtt (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test rabbitmq_mqtt / rabbitmq_mqtt (parallel-ct-set-1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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/
|
|
Test mixed clusters (28, 1.18) / Test plugins (rabbitmq_shovel) / rabbitmq_shovel (tests)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dsaltares/fetch-gh-release-asset@master, erlef/setup-beam@v1. 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 | |
|---|---|---|---|
|
CT logs (amqp10_client tests OTP-28 mixed)
|
409 KB |
sha256:f101f61e412ac296a183868491850f50f663eb6f688951b95572449e15bb8b2d
|
|
|
CT logs (amqp10_client tests OTP-28 )
|
408 KB |
sha256:c8f72d5315d2cf14df32b47cb6998c75dd2f223619a007c309175014acaa9df0
|
|
|
CT logs (amqp10_common tests OTP-28 mixed)
|
231 KB |
sha256:ef95862c9126e5b3c27368aa15f5aee9034da843fdeee2a2f4a76434c3c8607d
|
|
|
CT logs (amqp10_common tests OTP-28 )
|
231 KB |
sha256:d660ca0cab93911c322021c44b35d3e2bc3f39a57aa6ddd14500c2843211755b
|
|
|
CT logs (amqp_client tests OTP-28 mixed)
|
5.95 MB |
sha256:42fdba8da1cec1117e66681d4f927cf17036fbbaac218a81a178edafcbf0629c
|
|
|
CT logs (amqp_client tests OTP-28 )
|
5.85 MB |
sha256:f8c0784b5e4bf8da9cc0adf303231b29cdb118dfb924ab1be1361c2ede3910e2
|
|
|
CT logs (oauth2_client tests OTP-28 mixed)
|
409 KB |
sha256:b7a9242137c10993fe84784ccceee7254a966c935d1f270f6c93faec738fbf75
|
|
|
CT logs (oauth2_client tests OTP-28 )
|
409 KB |
sha256:28286e2fda1c2230424e39b176442333f9557ec18d054facd8b082a73963bf12
|
|
|
CT logs (rabbit ct-amqp_client OTP-28 mixed)
|
2.15 MB |
sha256:67ebd37d7aab52cbe8e9b64e5db80611f6ed0e686e869fcc058ab68c94e67a5b
|
|
|
CT logs (rabbit ct-amqp_client OTP-28 )
|
2.46 MB |
sha256:f9a2fabb893ab89b615e9406fac719dbdbf2155e9bdcab522c74002288a6748b
|
|
|
CT logs (rabbit ct-clustering_management OTP-28 mixed)
|
6.89 MB |
sha256:d66cf885a415f10fa97b8ee79d9348a70084318e7a3b56e562778fb011f88877
|
|
|
CT logs (rabbit ct-clustering_management OTP-28 )
|
5.8 MB |
sha256:5d88216d6376cec08d06c7c52701476f407749e5e5c1413ec36b61411c474a7b
|
|
|
CT logs (rabbit ct-clustering_recovery OTP-28 mixed)
|
6.62 MB |
sha256:bc44d93512710c81dc35ee7e162e45219b11539b30d9db8c086daacbc9097203
|
|
|
CT logs (rabbit ct-clustering_recovery OTP-28 )
|
6.2 MB |
sha256:d1e8e9a391d441094b88e72806bfbeb9c03e9854c85491b36ca0aadb96f2b80e
|
|
|
CT logs (rabbit ct-feature_flags OTP-28 mixed)
|
7.47 MB |
sha256:4e8c9412e4064f184598aa8d757baec0e3f1df844e9cdd42a13c49aca450435c
|
|
|
CT logs (rabbit ct-feature_flags OTP-28 )
|
6.84 MB |
sha256:e466769c13ae80e7c3d06997020f3a84941d65d339c4c6dbccde25fe5c54e061
|
|
|
CT logs (rabbit ct-metadata_store_clustering OTP-28 mixed)
|
131 KB |
sha256:22d5f362d376ab9aa16e655a80012feb135d67b4f7e75dcc1dcac89fbb46080c
|
|
|
CT logs (rabbit ct-metadata_store_clustering OTP-28 )
|
4.84 MB |
sha256:438ee60828e3d00db6b75fdc2d68d0406f8bd5904b53af2cd86c0dd0487c57d5
|
|
|
CT logs (rabbit ct-peer_discovery_classic_config OTP-28 mixed)
|
280 KB |
sha256:507aa16732d9df9ce95bfdb14ba29c73813305341ed6e64d0c7a4b72b541eff8
|
|
|
CT logs (rabbit ct-peer_discovery_classic_config OTP-28 )
|
2.32 MB |
sha256:4885ab7abdb3478bdb109114afb1a5a52ae66f9f69755f03bf105b380066d015
|
|
|
CT logs (rabbit ct-quorum_queue OTP-28 mixed)
|
3.67 MB |
sha256:29670174f6c9adbf76d64dfe84a5315e9a182cbe62a7bd635004f5aebe71fab0
|
|
|
CT logs (rabbit ct-quorum_queue OTP-28 )
|
5.73 MB |
sha256:d253458e1a1da8f97dc70155447a883986d13f4ad7c969c47b6e2ce9f724f5d8
|
|
|
CT logs (rabbit ct-rabbit_fifo_prop OTP-28 mixed)
|
389 KB |
sha256:3e7fca158b73c555e36e080aecab860a1cd1c572b5a727831dabe7d8aeea3dae
|
|
|
CT logs (rabbit ct-rabbit_fifo_prop OTP-28 )
|
389 KB |
sha256:8dbe64aa08a6acd2744759c96364326684727010e849ec14536271c1489d0a8d
|
|
|
CT logs (rabbit ct-rabbit_stream_queue OTP-28 mixed)
|
6.58 MB |
sha256:956c9b084128c64ab1f872385d291398c6ac240b6815d98b612867b17112f738
|
|
|
CT logs (rabbit ct-rabbit_stream_queue OTP-28 )
|
6.33 MB |
sha256:82564b47df9acb27bb6c068cdecbc35752521a82c09182fa11909b602ffc9a07
|
|
|
CT logs (rabbit eunit ct-dead_lettering OTP-28 mixed)
|
4.21 MB |
sha256:5ea35eb91cebf269549251face98f5fae9eeee3b83ffa4c401d344f062d32173
|
|
|
CT logs (rabbit eunit ct-dead_lettering OTP-28 )
|
4.12 MB |
sha256:05c0c9f40dfd49e713a4519505a7115d6abcb41b4a3a2cc7bc129f4d1f599a75
|
|
|
CT logs (rabbit parallel-ct-set-1 OTP-28 mixed)
|
11.3 MB |
sha256:02ece27d03292a3ec0978c85399bd2d0af862d8b5b10e882baf7277b2c8d7ae4
|
|
|
CT logs (rabbit parallel-ct-set-1 OTP-28 )
|
11.2 MB |
sha256:327f7295a5da3d4585a4a6376c7ec25a9ea3cefcf75379c256f93e3c2ef77931
|
|
|
CT logs (rabbit parallel-ct-set-2 OTP-28 mixed)
|
10 MB |
sha256:79f44825ceea253247998e446a431a80d75bd8662897ef17c423b70883a750fe
|
|
|
CT logs (rabbit parallel-ct-set-2 OTP-28 )
|
10.1 MB |
sha256:ba9c318b79e7cdaa31bce9f8ba6e1ebd3ea7653a929900731391031666583e89
|
|
|
CT logs (rabbit parallel-ct-set-3 OTP-28 mixed)
|
6.45 MB |
sha256:040b1074bf1319bbdb112d0799c1a39abfe8fc1126666642d903dab59a98a849
|
|
|
CT logs (rabbit parallel-ct-set-3 OTP-28 )
|
8.56 MB |
sha256:103e03dbcd38ddfab0bca510a5d6cd8545b84575e74ba3e86b9bf21166e0776d
|
|
|
CT logs (rabbit parallel-ct-set-4 OTP-28 mixed)
|
11.5 MB |
sha256:44a375347dffd6706f6ef4eade69fdf76c2dc46e9c2096d97c5df2f34d8ab4c2
|
|
|
CT logs (rabbit parallel-ct-set-4 OTP-28 )
|
11.5 MB |
sha256:9cace22091e1ee91f4e0b2d988004f8bb16b7c5a2d683ccbc02b21b5b0f11e0a
|
|
|
CT logs (rabbit parallel-ct-set-5 OTP-28 mixed)
|
6.36 MB |
sha256:e886bd2e889c1f785d4b407234df37463668eb1cab9596e0dc2faf24a07aea15
|
|
|
CT logs (rabbit parallel-ct-set-5 OTP-28 )
|
5.78 MB |
sha256:781ba322d1d7154c3d528343bd4eaceb71062d32d67adcb5647967d098395a5a
|
|
|
CT logs (rabbit_common tests OTP-28 mixed)
|
526 KB |
sha256:c542da146cfcbee65f05f3fe02ea96fe76aaea32851719ebb6a2cec6eca894b8
|
|
|
CT logs (rabbit_common tests OTP-28 )
|
526 KB |
sha256:5df068ab99c2edeccb5f5f6b582a4ecd6046a69578ec94baa5b8672e327916dc
|
|
|
CT logs (rabbitmq_amqp_client tests OTP-28 mixed)
|
822 KB |
sha256:eac5e6680aee4001525cf95637dbb8486bd4eab5c7b04603665f7b0a302f30db
|
|
|
CT logs (rabbitmq_amqp_client tests OTP-28 )
|
809 KB |
sha256:2ca382ab05b2c2db441afcb51cd92c2e7612bb7ef181f406c6f2c498647c1dd9
|
|
|
CT logs (rabbitmq_auth_backend_cache tests OTP-28 mixed)
|
554 KB |
sha256:eba704db22fa2868f1f2f2084d703b048909cab6e76a7bfe4f8a58ae0198d987
|
|
|
CT logs (rabbitmq_auth_backend_cache tests OTP-28 )
|
720 KB |
sha256:1852de264224dda4d8974b4a6cf7db606705fdce1dd14325f34d1c8ecaee549f
|
|
|
CT logs (rabbitmq_auth_backend_http tests OTP-28 mixed)
|
474 KB |
sha256:d74252360396a88263c9ec07c08f18f8752c2027abd3457a4c3424ab084c8b6d
|
|
|
CT logs (rabbitmq_auth_backend_http tests OTP-28 )
|
474 KB |
sha256:7d9144dbe3636ae8e20531963644b3d9e276570c1af0e534c651d41da8615f67
|
|
|
CT logs (rabbitmq_auth_backend_ldap tests OTP-28 mixed)
|
795 KB |
sha256:3e320ade200d8d5ded8e2063e424e2d7ea94374ab22b97b3d9882676212aa906
|
|
|
CT logs (rabbitmq_auth_backend_ldap tests OTP-28 )
|
796 KB |
sha256:f371da03cb8d96adfedd5483d20a501fb0e211d2d37259d17f84418a33410f59
|
|
|
CT logs (rabbitmq_auth_backend_oauth2 tests OTP-28 mixed)
|
2.74 MB |
sha256:8458560412847ce59c16be4a3ca28afdfd8772d3fdafa0b49dc368b8c8295fb7
|
|
|
CT logs (rabbitmq_auth_backend_oauth2 tests OTP-28 )
|
2.73 MB |
sha256:83a504ac18eadfee032d673274c34d3fd3c090c3cc48142aebcbe40d8984860e
|
|
|
CT logs (rabbitmq_auth_mechanism_ssl tests OTP-28 mixed)
|
230 KB |
sha256:d97958458409e143ab2e7b963517f7a048d4ed5fce3ea2e30f554f8927c38f58
|
|
|
CT logs (rabbitmq_auth_mechanism_ssl tests OTP-28 )
|
230 KB |
sha256:4522dfb1919b25490ef7ae362104027ea0cd68d0160b47141ad1c880207de877
|
|
|
CT logs (rabbitmq_aws tests OTP-28 mixed)
|
215 KB |
sha256:235825043aca989a30a4e875fc2469f3db2e60ef3972d869c5fe513ebad8e88b
|
|
|
CT logs (rabbitmq_aws tests OTP-28 )
|
215 KB |
sha256:0a7d1c98bd41eaaefda0c018f597005aee6282f7c9e4eb5295e53ddc6e661f92
|
|
|
CT logs (rabbitmq_cli tests OTP-28 mixed)
|
557 KB |
sha256:d8736f521253dfbbc5b1924dbececf7d715ba7e210949f4a106a1cb4f54d1ba8
|
|
|
CT logs (rabbitmq_cli tests OTP-28 )
|
487 KB |
sha256:296b7ea026b555f4096ce0ff4be30bfefc154aa00bd3612569919455ccd1d376
|
|
|
CT logs (rabbitmq_consistent_hash_exchange tests OTP-28 mixed)
|
1.42 MB |
sha256:bd026701c883e2f175e44159b8c14e42505e2b8ba0a7a168dd8f54484955bac5
|
|
|
CT logs (rabbitmq_consistent_hash_exchange tests OTP-28 )
|
1.38 MB |
sha256:c6cbd1a1059ff09c9a1d24c49e9b570f3c6e2b2637d38eb2c1cafd0dcfef1d19
|
|
|
CT logs (rabbitmq_event_exchange tests OTP-28 mixed)
|
650 KB |
sha256:2e3e8cc0399afaa69ae90ae587f1f6dfd42428eb4b04af53b107af7487c74e34
|
|
|
CT logs (rabbitmq_event_exchange tests OTP-28 )
|
649 KB |
sha256:70c021c65a70f8ad317d1ac2b226ac02f7bb749a92a7f318a13d00cfc6ab4d3f
|
|
|
CT logs (rabbitmq_exchange_federation tests OTP-28 mixed)
|
2.61 MB |
sha256:5b965998b8faa9635067c36a98ab5815723eed2ad93ff2c1205b912282e6cf0a
|
|
|
CT logs (rabbitmq_exchange_federation tests OTP-28 )
|
3.13 MB |
sha256:583e0144d56e94183e7e1bcb8eca4fea232312b6735b8f3301ef19077f7545e2
|
|
|
CT logs (rabbitmq_federation_common tests OTP-28 mixed)
|
278 KB |
sha256:1592ac84307f99b67a1e213bf0f59afac65fdb55d666a1806b33f8cdfaee7550
|
|
|
CT logs (rabbitmq_federation_common tests OTP-28 )
|
278 KB |
sha256:09fa37cb2f4c2aaaa05400aacdea87c1d0465c9d850d7a68480d9dcb53dafe7b
|
|
|
CT logs (rabbitmq_federation_management tests OTP-28 mixed)
|
310 KB |
sha256:e36b691a88694b24d1a56fb5d1a646697211ca9ae4a1623bd0d9e9507badce00
|
|
|
CT logs (rabbitmq_federation_management tests OTP-28 )
|
314 KB |
sha256:95744697d15d4e03f533d4f2e4174e71817e5c4a31b3fdb17540cc1807c776b0
|
|
|
CT logs (rabbitmq_federation_prometheus tests OTP-28 mixed)
|
260 KB |
sha256:7b923721854aa9813561d053a18061300b3acc2279a97f588ccb989549d8c0ae
|
|
|
CT logs (rabbitmq_federation_prometheus tests OTP-28 )
|
260 KB |
sha256:66cf1449e0cae02ee0e082b6e2e09da4da44f8a2ab98b95396befb1bc64f86e2
|
|
|
CT logs (rabbitmq_jms_topic_exchange tests OTP-28 mixed)
|
339 KB |
sha256:db808d95e144e22cdc65c580840160aa71ac6bfefffb9544639cf4eddd36b75c
|
|
|
CT logs (rabbitmq_jms_topic_exchange tests OTP-28 )
|
339 KB |
sha256:e940755ba485d0878f4f8d0c5a6b0265ff82d1c7678841893ebacda51c715698
|
|
|
CT logs (rabbitmq_management tests OTP-28 mixed)
|
7.37 MB |
sha256:4a60f248b6baecc7eaff0aace9c7e6f9d9d38f7ce9c81d837c073a4b648a146f
|
|
|
CT logs (rabbitmq_management tests OTP-28 )
|
7.33 MB |
sha256:ba27fee9508a42a6b0b4be2c39cbe98b76b3a675cd36d88011526960b0735f3a
|
|
|
CT logs (rabbitmq_management_agent tests OTP-28 mixed)
|
736 KB |
sha256:a937234b8e02d9ff20d9f351bb9bb29546cc686fe5469e2a32fec74fd4fea794
|
|
|
CT logs (rabbitmq_management_agent tests OTP-28 )
|
709 KB |
sha256:ac392481033bd9ee8821916bda15aec9803d1d09af327f587eed1e5fc0637448
|
|
|
CT logs (rabbitmq_mqtt parallel-ct-set-1 OTP-28 mixed)
|
12.4 MB |
sha256:bf3d76e4c2e11b6832250c059946df41fde15337e2efb2e99015240108b94dce
|
|
|
CT logs (rabbitmq_mqtt parallel-ct-set-1 OTP-28 )
|
11.9 MB |
sha256:7d475f82e7f90d64dc40527b07e8ab31c82d87c7a9d1e766b44e053eeb27da53
|
|
|
CT logs (rabbitmq_peer_discovery_aws ct-config_schema ct-unit OTP-28 mixed)
|
348 KB |
sha256:9ea47bb714f0f5753e891d2070b35781304340c972fd7c55d5d7db05a50a925b
|
|
|
CT logs (rabbitmq_peer_discovery_aws ct-config_schema ct-unit OTP-28 )
|
348 KB |
sha256:d6268e475e60dd39438a9fb92ccb7cb2766e4e4c236341e31b3553a905128b8b
|
|
|
CT logs (rabbitmq_peer_discovery_common tests OTP-28 mixed)
|
874 KB |
sha256:89535c3412ba2d0e39f016edd8c6686c8278ffce2bf43388cc43e4972c2162ba
|
|
|
CT logs (rabbitmq_peer_discovery_common tests OTP-28 )
|
846 KB |
sha256:0f798f2009e06752616d823e469124782e49a061e6bc8c520cdf348f9f9df345
|
|
|
CT logs (rabbitmq_peer_discovery_consul tests OTP-28 mixed)
|
1.08 MB |
sha256:669cab0e514dd76c6ecc822629ae4984b185d05c6038ba3e3542117092dd7a4f
|
|
|
CT logs (rabbitmq_peer_discovery_consul tests OTP-28 )
|
1.08 MB |
sha256:6e6f2144bf0c977374eb8696063ce6b362d0979902c783a4ae04c7a783d528f4
|
|
|
CT logs (rabbitmq_peer_discovery_etcd tests OTP-28 mixed)
|
1.04 MB |
sha256:43510e4359768b062537dff8c1dd61808709a9463d67fd50d2ee2e1b2eb84e0b
|
|
|
CT logs (rabbitmq_peer_discovery_etcd tests OTP-28 )
|
1.05 MB |
sha256:ed1b64d9c05bdd8b21cce602e6d7e737401080d318f2605b63f78d6dd142670f
|
|
|
CT logs (rabbitmq_peer_discovery_k8s tests OTP-28 mixed)
|
278 KB |
sha256:0f9fb5951db40bd7ac1fe31791fd75afdee6094669a060d4b11ab82c78289938
|
|
|
CT logs (rabbitmq_peer_discovery_k8s tests OTP-28 )
|
278 KB |
sha256:74b0e19bd490427c53285d3903adde7c4e85cbd3c1e45ee8b85451cd9f48d378
|
|
|
CT logs (rabbitmq_prometheus tests OTP-28 mixed)
|
1.92 MB |
sha256:cec2d63317d99b1e6acf5af5fff7677bdc7efe4e4303c7dfc8df46d0eb8ffd48
|
|
|
CT logs (rabbitmq_prometheus tests OTP-28 )
|
1.92 MB |
sha256:53f73827558369a6fda0324a03edaffcd5a16c4a67709782cc96411d700960d3
|
|
|
CT logs (rabbitmq_queue_federation tests OTP-28 mixed)
|
1.72 MB |
sha256:ee4c29fa93e2b770ffe628da867f8ece091b369b2aa3253a2baa6a599bc6ba95
|
|
|
CT logs (rabbitmq_queue_federation tests OTP-28 )
|
2.17 MB |
sha256:1d1532aaa420024cc46a1afb673797c63e46790f375ebc3e4957b649ffec7e3d
|
|
|
CT logs (rabbitmq_recent_history_exchange tests OTP-28 mixed)
|
588 KB |
sha256:37c945b5fd84b614393f3de856ded0435549e6f4885b8d16d11638877316a08f
|
|
|
CT logs (rabbitmq_recent_history_exchange tests OTP-28 )
|
561 KB |
sha256:61513f2525bcfcc898eea2e0cb2ddbebf98e6264561ea1cb93ebb1595ecb22e0
|
|
|
CT logs (rabbitmq_sharding tests OTP-28 mixed)
|
984 KB |
sha256:84e3fe2ee44245746deb85aac0796ceac62b6d177c7b4c8a2f1e16a6bea43da4
|
|
|
CT logs (rabbitmq_sharding tests OTP-28 )
|
939 KB |
sha256:8e7fbf85b1f0ad99dfeb246965973c6330eefb9f5def96f75e8a9f9eeb88d09f
|
|
|
CT logs (rabbitmq_shovel tests OTP-28 mixed)
|
20.5 MB |
sha256:e223adfcc012a266e440b81f84b6e330450bf917e0b445e8c3a186736b147c94
|
|
|
CT logs (rabbitmq_shovel tests OTP-28 )
|
20.4 MB |
sha256:3bfc317cb23133a741c8010c510faa2d810a58034630d09f8ac0b53d104104de
|
|
|
CT logs (rabbitmq_shovel_management tests OTP-28 mixed)
|
436 KB |
sha256:b02801cba3c3e65f7dcc82365da684ca7ff861071477bb354e79aba9279e5f59
|
|
|
CT logs (rabbitmq_shovel_management tests OTP-28 )
|
438 KB |
sha256:add85c01eb2ed1a6a6aef38ee2e73a5bcd7ad30dc61fd2c1eb043297bed50145
|
|
|
CT logs (rabbitmq_shovel_prometheus tests OTP-28 mixed)
|
255 KB |
sha256:567dc5402cac4107fb12dc570e7f53eff890be8f8b9eed498cca1c1cbd4341e8
|
|
|
CT logs (rabbitmq_shovel_prometheus tests OTP-28 )
|
254 KB |
sha256:92c473c5d0d60a31040bb68684afc460de54547b473494fd0810b0c11a48b7ca
|
|
|
CT logs (rabbitmq_stomp tests OTP-28 mixed)
|
1.5 MB |
sha256:fc60551aec596523f1e415a0070fa953865c6897023c73ba3add33524564e17e
|
|
|
CT logs (rabbitmq_stomp tests OTP-28 )
|
1.5 MB |
sha256:f8cb6354204499b5638aa7a08626a93549d16a237608cf27bb996668069677a4
|
|
|
CT logs (rabbitmq_stream tests OTP-28 mixed)
|
577 KB |
sha256:39793f64277e90f496d4ca95fc62591b9e78ab16000afe19240b695d5e2bffdd
|
|
|
CT logs (rabbitmq_stream tests OTP-28 )
|
3.02 MB |
sha256:239c693e5c2891a3e3b96bf54a2c3dd00b745ff3e563f4045717169b464be66b
|
|
|
CT logs (rabbitmq_stream_common tests OTP-28 mixed)
|
132 KB |
sha256:ea0963cb0120bbafda38ae13b450dad8aa1af4a2b80cce490f263aed89a2d201
|
|
|
CT logs (rabbitmq_stream_common tests OTP-28 )
|
132 KB |
sha256:ffc906338a1a682ff0a4a502dbbc79f934348633f975083dcf8ffb06be15c831
|
|
|
CT logs (rabbitmq_stream_management tests OTP-28 mixed)
|
120 KB |
sha256:46965b9da9ebed3b9558fe49af6eae80b4110178a1ee1721764b7d54455517e3
|
|
|
CT logs (rabbitmq_stream_management tests OTP-28 )
|
329 KB |
sha256:d068bc7649d9b298936abdbdec5bca2d24ac17e4de47eed745dd41250c793a27
|
|
|
CT logs (rabbitmq_tracing tests OTP-28 mixed)
|
354 KB |
sha256:3d467849b30f18354adaa297d9f6b4e357bbc7cc10135fdec81ae5ee82a8d4a3
|
|
|
CT logs (rabbitmq_tracing tests OTP-28 )
|
354 KB |
sha256:afa0a9e7012f942a0b6d3349db09d89a01e97b86c1fcdc32808f9c532d249acc
|
|
|
CT logs (rabbitmq_trust_store tests OTP-28 mixed)
|
563 KB |
sha256:c5f0dce8f20e2fa25cb38e52708a8b21fd4e2d3f8fe449c8710aa5539ac36293
|
|
|
CT logs (rabbitmq_trust_store tests OTP-28 )
|
563 KB |
sha256:6c9faaaae65fc22c9418f296087fcb8def76468920435ff7ed585e78f12ef49c
|
|
|
CT logs (rabbitmq_web_dispatch tests OTP-28 mixed)
|
389 KB |
sha256:99109753bcde5414566a082450a7f0c23e90c53ae91095047323a74644b566e7
|
|
|
CT logs (rabbitmq_web_dispatch tests OTP-28 )
|
389 KB |
sha256:8afa12fb5ab71cad5cd93802048c9eec28222029fcf187a470d8bf492687f5a2
|
|
|
CT logs (rabbitmq_web_mqtt tests OTP-28 mixed)
|
4.02 MB |
sha256:8dff672cdd603cea733069752e89866c468d425ebfbe2bf5d952b81c4b9e25c4
|
|
|
CT logs (rabbitmq_web_mqtt tests OTP-28 )
|
3.83 MB |
sha256:101345dee93501b76fbdb64094e76649e736ba458e0eb9d817de540ae603221a
|
|
|
CT logs (rabbitmq_web_stomp tests OTP-28 mixed)
|
976 KB |
sha256:f19655373265aa2bc44b5f5fd48dc4a94c7e61696e3fa9ba9cf0d7aa9db917c6
|
|
|
CT logs (rabbitmq_web_stomp tests OTP-28 )
|
975 KB |
sha256:e0892537424927ff56ea3b36ddcc3ea68c286588836f64d4c9326aa5da4c8c8e
|
|