Merge pull request #15688 from rabbitmq/mergify/bp/v4.2.x/pr-15687 #7052
test-make.yaml
on: push
Matrix: Build and Xref
Matrix: Test mixed clusters
Matrix: Test
Matrix: Type check
Annotations
290 warnings
|
Test (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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/
|
|
Test (28, 1.18, mnesia) / 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/
|
|
Test mixed clusters (28, 1.18, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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/
|
|
Test mixed clusters (28, 1.18, mnesia) / 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/
|
|
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, khepri) / 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, khepri) / 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 (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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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 (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/
|
|
Test mixed clusters (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 (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 (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 (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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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/
|
|
Test (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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 mixed clusters (28, 1.18, mnesia) / 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 (28, 1.18, khepri) / 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, khepri) / 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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 mixed clusters (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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, mnesia) / 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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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, mnesia) / 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 mixed clusters (28, 1.18, khepri) / 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, mnesia) / 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 mixed clusters (28, 1.18, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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 (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 mixed clusters (28, 1.18, mnesia) / 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, khepri) / 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, mnesia) / 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 mixed clusters (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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, mnesia) / 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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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 (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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, khepri) / 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, khepri) / 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 mixed clusters (28, 1.18, mnesia) / 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 (28, 1.18, mnesia) / 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 (28, 1.18, khepri) / 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, mnesia) / 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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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 (28, 1.18, mnesia) / 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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 (28, 1.18, khepri) / 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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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/
|
|
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/
|
|
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_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 mixed clusters (28, 1.18, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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/
|
|
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_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_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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 mixed clusters (28, 1.18, mnesia) / 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 (28, 1.18, khepri) / 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 (28, 1.18, khepri) / 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 mixed clusters (28, 1.18, mnesia) / 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/
|
|
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/
|
|
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/
|
|
Test (28, 1.18, khepri) / 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/
|
|
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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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_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_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/
|
|
Test (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 (28, 1.18, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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, khepri) / 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/
|
|
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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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/
|
|
Test mixed clusters (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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/
|
|
Test (28, 1.18, mnesia) / 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/
|
|
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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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_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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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_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_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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 mixed clusters (28, 1.18, khepri) / 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 (28, 1.18, mnesia) / 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_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/
|
|
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/
|
|
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/
|
|
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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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/
|
|
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_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, khepri) / 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/
|
|
Test (28, 1.18, khepri) / 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 mixed clusters (28, 1.18, mnesia) / 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 (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_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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 (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/
|
|
Test mixed clusters (28, 1.18, khepri) / 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_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_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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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 mixed clusters (28, 1.18, mnesia) / 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 mixed clusters (28, 1.18, khepri) / 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/
|
|
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.19. 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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.19. 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, mnesia) / 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 (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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.19. 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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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 (28, 1.18, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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/
|
|
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/
|
|
Test mixed clusters (28, 1.18, mnesia) / 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/
|
|
Test mixed clusters (28, 1.18, khepri) / 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/
|
|
Test mixed clusters (28, 1.18, khepri) / 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/
|
|
Test (28, 1.18, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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/
|
|
Test (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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/
|
|
Test (28, 1.18, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 mixed clusters (28, 1.18, khepri) / 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 (28, 1.18, mnesia) / 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, mnesia) / 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 (28, 1.18, mnesia) / 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/
|
|
Test mixed clusters (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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/
|
|
Test (28, 1.18, mnesia) / 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, khepri) / 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 mixed clusters (28, 1.18, khepri) / 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/
|
|
Test (28, 1.18, khepri) / 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, khepri) / 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 mixed clusters (28, 1.18, mnesia) / 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 mixed clusters (28, 1.18, khepri) / 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, mnesia) / 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/
|
|
Test mixed clusters (28, 1.18, mnesia) / 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 (28, 1.18, khepri) / 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, khepri) / 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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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, mnesia) / 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, mnesia) / 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/
|
|
Test (28, 1.18, khepri) / 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/
|
|
Test mixed clusters (28, 1.18, khepri) / 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/
|
|
Test mixed clusters (28, 1.18, mnesia) / 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/
|
|
Test (28, 1.18, mnesia) / 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, khepri) / 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 mixed clusters (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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/
|
|
Test mixed clusters (28, 1.18, khepri) / 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, mnesia) / 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/
|
|
Test (28, 1.18, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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, khepri) / 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, khepri) / 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, mnesia) / 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 (28, 1.18, khepri) / 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 (28, 1.18, mnesia) / 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, khepri) / 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, mnesia) / 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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 mixed clusters (28, 1.18, mnesia) / 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 (28, 1.18, khepri) / 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 mixed clusters (28, 1.18, mnesia) / 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 (28, 1.18, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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, khepri) / 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, mnesia) / 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, khepri) / 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, khepri) / 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, mnesia) / 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 mixed clusters (28, 1.18, khepri) / 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 mixed clusters (28, 1.18, mnesia) / 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, mnesia) / 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, khepri) / 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 mixed clusters (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 mixed clusters (28, 1.18, khepri) / 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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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, khepri) / 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, khepri) / 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, mnesia) / 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 mixed clusters (28, 1.18, mnesia) / 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, khepri) / 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 mixed clusters (28, 1.18, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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 (28, 1.18, khepri) / 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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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 (28, 1.18, mnesia) / 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 (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 (28, 1.18, khepri) / 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 mixed clusters (28, 1.18, mnesia) / 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 mixed clusters (28, 1.18, mnesia) / 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/
|
|
Test (28, 1.18, mnesia) / 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, mnesia) / 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 (28, 1.18, khepri) / 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, mnesia) / 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, khepri) / 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 mixed clusters (28, 1.18, khepri) / 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/
|
|
Test mixed clusters (28, 1.18, khepri) / 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 (28, 1.18, mnesia) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, mnesia) / 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 mixed clusters (28, 1.18, mnesia) / 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, mnesia) / 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, mnesia) / 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, khepri) / 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 (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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, mnesia) / 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 (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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 (28, 1.18, mnesia) / 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, khepri) / 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 (28, 1.18, khepri) / 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 (28, 1.18, khepri) / 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. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_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, khepri) / 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, mnesia) / 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 (28, 1.18, khepri) / 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
CT logs (amqp10_client tests OTP-28 khepri mixed)
Expired
|
421 KB |
sha256:c6c85cff5c37a9db66aee574ba51f31d41afb022721077b5e688a9fd602ebe92
|
|
|
CT logs (amqp10_client tests OTP-28 khepri)
Expired
|
420 KB |
sha256:730c68ab0d3e1c2fd2c6e5b39daf3cc4a54f66aef2ec4ea721fdc54f792c8920
|
|
|
CT logs (amqp10_client tests OTP-28 mnesia mixed)
Expired
|
409 KB |
sha256:7d40ca9521821bb663be073509eea4fdb242c80200ee10ba2d47670519efa7e3
|
|
|
CT logs (amqp10_client tests OTP-28 mnesia)
Expired
|
408 KB |
sha256:d92f70fc6ec7b3b391ffc4ce1196ea59066db564595b9129930927d98d849ad1
|
|
|
CT logs (amqp10_common tests OTP-28 khepri mixed)
Expired
|
231 KB |
sha256:5084dda2fd7fd5c154225bbf7725c176339b9eba8b96f6273cd20b30bccff6ef
|
|
|
CT logs (amqp10_common tests OTP-28 khepri)
Expired
|
231 KB |
sha256:15875d08093d2e400689945b419c16b553a6b28c43af7dd4400e0ecbb2152e9e
|
|
|
CT logs (amqp10_common tests OTP-28 mnesia mixed)
Expired
|
231 KB |
sha256:1cc5ede950fc55fd3878b2a2e4273d41e5f93be511b14b017bf6d4f1bccb770b
|
|
|
CT logs (amqp10_common tests OTP-28 mnesia)
Expired
|
231 KB |
sha256:158be8307102704fd1c38f646ce418dd7f067322cd4612680dbb94e2042bc1ec
|
|
|
CT logs (amqp_client tests OTP-28 khepri mixed)
Expired
|
6.73 MB |
sha256:82b8734f4de4e11e9cbca765b9d891073b6a179dc8af301f14e40d56f888823a
|
|
|
CT logs (amqp_client tests OTP-28 khepri)
Expired
|
6.74 MB |
sha256:8ab2225787269a3c819c725137f21595888119bee1afaf51f582dec8280eb493
|
|
|
CT logs (amqp_client tests OTP-28 mnesia mixed)
Expired
|
6.32 MB |
sha256:2bcd79829302251b1715e184d0243783726ed13299e371852721670ad2e54dad
|
|
|
CT logs (amqp_client tests OTP-28 mnesia)
Expired
|
6.29 MB |
sha256:01e30657b6f70ae6d282ad6d0aaa2e8cc217fca7962393f700942510cdf13141
|
|
|
CT logs (oauth2_client tests OTP-28 khepri mixed)
Expired
|
402 KB |
sha256:b0b1f611c2e750245ae11b5469bfa901a9c87f9d52a9c29b731d6376926062d8
|
|
|
CT logs (oauth2_client tests OTP-28 khepri)
Expired
|
401 KB |
sha256:7eeaf2c9bc1edf1c6d35e83ccca2ea7cdda1b08e7b2ce8a76336920cd611a10c
|
|
|
CT logs (oauth2_client tests OTP-28 mnesia mixed)
Expired
|
402 KB |
sha256:9cb347bac0c5ab7724ab29bfd1c8e7008d563f5d694aa7575a178bf635cf801d
|
|
|
CT logs (oauth2_client tests OTP-28 mnesia)
Expired
|
401 KB |
sha256:29028c34a36472a48805a97fb6fc1d33b91c2ec966421d7b93892aef4b939791
|
|
|
CT logs (rabbit ct-amqp_client OTP-28 khepri mixed)
Expired
|
2.21 MB |
sha256:1911a6cb4475570e086e53251b01638c90b96357e3e4a633241e45b10e3f6a14
|
|
|
CT logs (rabbit ct-amqp_client OTP-28 khepri)
Expired
|
2.16 MB |
sha256:f6c97149e41107ea21a8b3b41ca9c4febf740afe74bc96fb9482db75c6c9bfba
|
|
|
CT logs (rabbit ct-amqp_client OTP-28 mnesia mixed)
Expired
|
1.69 MB |
sha256:9fd3e82f5f2d37b4ef311183c47c19caf7547ea41b8c81a134cf0a82c6a24e74
|
|
|
CT logs (rabbit ct-amqp_client OTP-28 mnesia)
Expired
|
2.19 MB |
sha256:b6e2bfd2284add5c5cea634442c1b89a170b891ac195b2d9d1a8f18310a0ef19
|
|
|
CT logs (rabbit ct-clustering_management OTP-28 khepri mixed)
Expired
|
6.22 MB |
sha256:e700f088d4c947cb421b07d33ff36accf3dbed448fe0ce0ae37ce65c2f25d03e
|
|
|
CT logs (rabbit ct-clustering_management OTP-28 khepri)
Expired
|
6.26 MB |
sha256:c8a3dcda490d480e535983a0f5fbf9555424f10421992ab7ba7f99195af146e8
|
|
|
CT logs (rabbit ct-clustering_management OTP-28 mnesia mixed)
Expired
|
4.3 MB |
sha256:1191294327d3839120b3d977571e9920a1f034c8ad00334e190884321195202e
|
|
|
CT logs (rabbit ct-clustering_management OTP-28 mnesia)
Expired
|
4.24 MB |
sha256:40f0b8b30218803bd8e65c2a042d55d400df978c37e9d19ce5955c58fad2794c
|
|
|
CT logs (rabbit ct-clustering_recovery OTP-28 khepri mixed)
Expired
|
8.52 MB |
sha256:07670654b9a35a0a51c88289a5773f0cc632ff226e6692bd1b01caeef3ab55ca
|
|
|
CT logs (rabbit ct-clustering_recovery OTP-28 khepri)
Expired
|
7.55 MB |
sha256:23503b4e10c711eaf85b777c32d1403846a6e5542007bcffc3784535feabcfa2
|
|
|
CT logs (rabbit ct-clustering_recovery OTP-28 mnesia mixed)
Expired
|
2.86 MB |
sha256:2ad97f6fa81536041e8cb8f0d3b2ebaa450d045fe8f7a132d51674b48e0df230
|
|
|
CT logs (rabbit ct-clustering_recovery OTP-28 mnesia)
Expired
|
2.94 MB |
sha256:d9f12051548eeb2ed9fa214458e39d56beac49a3a6371f33a8b4ce0ad4a5525b
|
|
|
CT logs (rabbit ct-feature_flags OTP-28 khepri mixed)
Expired
|
7.26 MB |
sha256:323a74544331ab97098bf64ff60d79978c6565b922a5e75bebbb14ce02eb2c4d
|
|
|
CT logs (rabbit ct-feature_flags OTP-28 khepri)
Expired
|
7.47 MB |
sha256:ffedec0bf1403fc1749a4556e104cb9d05af5f8240ec4567b40a6ece05083821
|
|
|
CT logs (rabbit ct-feature_flags OTP-28 mnesia mixed)
Expired
|
6.22 MB |
sha256:a5db1129354ca1d85cdf73f8ccbe47ba34bcff33f3bd07429f83c0492c1d4040
|
|
|
CT logs (rabbit ct-feature_flags OTP-28 mnesia)
Expired
|
6.15 MB |
sha256:7a3a7cb93964337c00350abb330ccf520ea91e400499c256653ff13537b82e76
|
|
|
CT logs (rabbit ct-metadata_store_clustering OTP-28 khepri mixed)
Expired
|
131 KB |
sha256:ec0198730498dfb7db5d002196de58154837d35ef17d6b96cbbea230ea2172de
|
|
|
CT logs (rabbit ct-metadata_store_clustering OTP-28 khepri)
Expired
|
4.89 MB |
sha256:c170378e075c8695bea78bc75d13175ed4f7aa2d1f36d69519c2e5d75af2619f
|
|
|
CT logs (rabbit ct-metadata_store_clustering OTP-28 mnesia mixed)
Expired
|
131 KB |
sha256:438dc18e070964afd18f2149adb8a245d2d28315b1faf5d3a0991128e4b4be46
|
|
|
CT logs (rabbit ct-metadata_store_clustering OTP-28 mnesia)
Expired
|
4.9 MB |
sha256:1238af1880a1688aaa6bf238083e20fb70e08f091c9ee188dc060259cffdd84e
|
|
|
CT logs (rabbit ct-peer_discovery_classic_config OTP-28 khepri mixed)
Expired
|
280 KB |
sha256:844b167f4bdd7e9f5fe1c7a5d7e28f0827e3019744619de4586e04b8575c0c20
|
|
|
CT logs (rabbit ct-peer_discovery_classic_config OTP-28 khepri)
Expired
|
2.46 MB |
sha256:59059d9edf1f36e9fe79a298bac84374d64166b4911b072c9d591681fe4bbc66
|
|
|
CT logs (rabbit ct-peer_discovery_classic_config OTP-28 mnesia mixed)
Expired
|
282 KB |
sha256:633bd98a9e2187cbfabf2b06bcbc983fac00dd13aca23d2490e77c8e3d225904
|
|
|
CT logs (rabbit ct-peer_discovery_classic_config OTP-28 mnesia)
Expired
|
2.19 MB |
sha256:19b11a152f8022193dc9760169fe2e1963422166ee9883902131b4ef2d06571b
|
|
|
CT logs (rabbit ct-quorum_queue OTP-28 khepri mixed)
Expired
|
3.55 MB |
sha256:21510d5f04d32fca6576688d6bdd5aaa6517254315ef42da0327dd21c80fc12d
|
|
|
CT logs (rabbit ct-quorum_queue OTP-28 khepri)
Expired
|
5.86 MB |
sha256:d5876b68a6643991c84c5ea0ec40b78c7cf26387261a17294e7b8a41c10fc83a
|
|
|
CT logs (rabbit ct-quorum_queue OTP-28 mnesia mixed)
Expired
|
2.47 MB |
sha256:084245f00babf5b96f5a5a717d52fd7cf74f21d0e08c5efd4df7de3d7441b53b
|
|
|
CT logs (rabbit ct-quorum_queue OTP-28 mnesia)
Expired
|
4.38 MB |
sha256:2c50f219bdc5ab2daaec29f8ad6839a43532d91cc9c3d242bb4f377392987d30
|
|
|
CT logs (rabbit ct-rabbit_fifo_prop OTP-28 khepri mixed)
Expired
|
393 KB |
sha256:60fa8e46394edabf8a42dffaf7f72fe725063bc68c155298d141a0e8593de464
|
|
|
CT logs (rabbit ct-rabbit_fifo_prop OTP-28 khepri)
Expired
|
395 KB |
sha256:78f6697113ae9d13387bf330129699263a51ba2a7eef2e2c4845e22e8c25148f
|
|
|
CT logs (rabbit ct-rabbit_fifo_prop OTP-28 mnesia mixed)
Expired
|
392 KB |
sha256:6f2d9a38a6e93162c83b6868868e549d3b48a547ea78d4653dc0af366d0efb0d
|
|
|
CT logs (rabbit ct-rabbit_fifo_prop OTP-28 mnesia)
Expired
|
394 KB |
sha256:503f8fcc0752b39f2d8f332b805c8a93a138f6be2792daf81d4fb02fa06cf7e0
|
|
|
CT logs (rabbit ct-rabbit_stream_queue OTP-28 khepri mixed)
Expired
|
6.5 MB |
sha256:19c5c95b753c6ae353c1ed3c349d33a74170752850ea814650347cd0c73048e0
|
|
|
CT logs (rabbit ct-rabbit_stream_queue OTP-28 khepri)
Expired
|
6.47 MB |
sha256:109ee5e1c887024da02f149b6d817cd4e11cd05677f233a81fa589d9d25817d4
|
|
|
CT logs (rabbit ct-rabbit_stream_queue OTP-28 mnesia mixed)
Expired
|
5.52 MB |
sha256:1356ba15a94e1b9c4dc6d4598aabcc91a030de20db152f1842f6c5a2f9f157e0
|
|
|
CT logs (rabbit ct-rabbit_stream_queue OTP-28 mnesia)
Expired
|
5.63 MB |
sha256:3fb400c067f420c984eeeb219903f0cb936b489e061ff288a74261483aeffa80
|
|
|
CT logs (rabbit eunit ct-dead_lettering OTP-28 khepri mixed)
Expired
|
4.21 MB |
sha256:398f841c955270abc5a52147c1e3f3e2b56f27b23db6b33146eaad97b06136a3
|
|
|
CT logs (rabbit eunit ct-dead_lettering OTP-28 khepri)
Expired
|
4.22 MB |
sha256:3434d874048a15f758280b5a753e786ca7af3e22f028a8dbacbf25d342aa34f3
|
|
|
CT logs (rabbit eunit ct-dead_lettering OTP-28 mnesia mixed)
Expired
|
1.42 MB |
sha256:e92f85b9cf8acc7f1745c30a82ae0d122efb7d9f4c02ed609d6e95e043e48c8f
|
|
|
CT logs (rabbit eunit ct-dead_lettering OTP-28 mnesia)
Expired
|
1.4 MB |
sha256:3adb86a72e98337e16637c3b35ea88b38e4224071291627a73fd7757ec2c2805
|
|
|
CT logs (rabbit parallel-ct-set-1 OTP-28 khepri mixed)
Expired
|
11.5 MB |
sha256:e4c1abe0f341ebb1e9ae3bd3e7f4616f3ba06f31a94d2f274beb75e19141b28d
|
|
|
CT logs (rabbit parallel-ct-set-1 OTP-28 khepri)
Expired
|
12.1 MB |
sha256:42fba88a01ee5c5868f8ca9f52915e31fcf3548e6b4f442e27f209af458dbf6e
|
|
|
CT logs (rabbit parallel-ct-set-1 OTP-28 mnesia mixed)
Expired
|
8.09 MB |
sha256:7f02723f5fb09461e0d3819ad07a4968cbebac00af3af1287f635fb860e858e3
|
|
|
CT logs (rabbit parallel-ct-set-1 OTP-28 mnesia)
Expired
|
8.62 MB |
sha256:ab27353dc57b9dc5d21da5430aa7a28f66282e07905952c343c063bb820e03a3
|
|
|
CT logs (rabbit parallel-ct-set-2 OTP-28 khepri mixed)
Expired
|
11 MB |
sha256:00e3ce5477793a6d5ea223e453bcc6cd8247847be9781603a630e3c5bf59bc29
|
|
|
CT logs (rabbit parallel-ct-set-2 OTP-28 khepri)
Expired
|
11.2 MB |
sha256:46817b3394f89c236b4ba7229100a15e74c40e9da794b3de37faffbc12d7bace
|
|
|
CT logs (rabbit parallel-ct-set-2 OTP-28 mnesia mixed)
Expired
|
10.5 MB |
sha256:d301caf859c6f34e339772a3e54e1cac71444d315aaefa7275ccb037488f18b7
|
|
|
CT logs (rabbit parallel-ct-set-2 OTP-28 mnesia)
Expired
|
10.7 MB |
sha256:c375208750abac67eef1013cadadf232e970ad4af4fa961150e3c084d8466cff
|
|
|
CT logs (rabbit parallel-ct-set-3 OTP-28 khepri mixed)
Expired
|
7.19 MB |
sha256:a8adf055dfe0012ef2b85179f7b71732a683ed90257ff50c68d701bd016f8360
|
|
|
CT logs (rabbit parallel-ct-set-3 OTP-28 khepri)
Expired
|
9.68 MB |
sha256:8a5cc14c4c7c9a9fa1ac68bfbc3fda94b0b52b3f3ff0b8760b0e1303c21f1245
|
|
|
CT logs (rabbit parallel-ct-set-3 OTP-28 mnesia mixed)
Expired
|
6.69 MB |
sha256:4eed84693dc1db640aa240dc9610f0110262e31ed1110f1377e3c2587618285b
|
|
|
CT logs (rabbit parallel-ct-set-3 OTP-28 mnesia)
Expired
|
9.48 MB |
sha256:bc9130ae1904ec99b55dc9f530d2a2f2a8ed12bf969ae5a2e679abf201eaccb8
|
|
|
CT logs (rabbit parallel-ct-set-4 OTP-28 khepri mixed)
Expired
|
11.9 MB |
sha256:691b4e89cbfc8c925d84e82563cfcaeb04848f20f5e5b60a52e576686296ece4
|
|
|
CT logs (rabbit parallel-ct-set-4 OTP-28 khepri)
Expired
|
12.7 MB |
sha256:9f6d92f72806bfe56daa34d2df6bb2cf8d4213357dd32933e2d9d8e54fd53ace
|
|
|
CT logs (rabbit parallel-ct-set-4 OTP-28 mnesia mixed)
Expired
|
10.5 MB |
sha256:25fc500fbf1c953e2ce203344727d15c4f627c8f9ae5e1a337872e297babdee7
|
|
|
CT logs (rabbit parallel-ct-set-4 OTP-28 mnesia)
Expired
|
11.1 MB |
sha256:b9deb9e0b89baa170521c8f4c3987e375181931f1187349856686dd3599489d5
|
|
|
CT logs (rabbit parallel-ct-set-5 OTP-28 khepri mixed)
Expired
|
6.22 MB |
sha256:0ace39c7c82537fd795b1f221458af902b6fa9fdbfabc2f396501337c7f0ffd6
|
|
|
CT logs (rabbit parallel-ct-set-5 OTP-28 khepri)
Expired
|
5.88 MB |
sha256:0b777e9f402c28ab5b83bec4ca670ddb4a485be769913616780acbf1452e56f5
|
|
|
CT logs (rabbit parallel-ct-set-5 OTP-28 mnesia mixed)
Expired
|
5.43 MB |
sha256:b48b4349e0aaab1fe339599b441a1a48fdedf9fb5aac5c1190172775495e53db
|
|
|
CT logs (rabbit parallel-ct-set-5 OTP-28 mnesia)
Expired
|
5.18 MB |
sha256:e6896a23cbb61898b4a3809776322926092ce93ddc26d79ed4b0ff8dcdcd451e
|
|
|
CT logs (rabbit_common tests OTP-28 khepri mixed)
Expired
|
524 KB |
sha256:20200f5b0ee7b7d3d7f590fdc2f3fb2e04721878669922332d0fb6596d99416f
|
|
|
CT logs (rabbit_common tests OTP-28 khepri)
Expired
|
524 KB |
sha256:a1cd5c452145019763ae343a47ae223aada950a7fa3da0f4072aead366b0f0c9
|
|
|
CT logs (rabbit_common tests OTP-28 mnesia mixed)
Expired
|
524 KB |
sha256:3114d5b38f6ea0afba38be0073a2d2a322d3f56e7061ed9a0834a7a9a6fb43c6
|
|
|
CT logs (rabbit_common tests OTP-28 mnesia)
Expired
|
524 KB |
sha256:1748594d695bdd61e473c546aebf21140d4034b8b9c2cd761822f9b8be3afce8
|
|
|
CT logs (rabbitmq_amqp_client tests OTP-28 khepri mixed)
Expired
|
841 KB |
sha256:03e65d4ac1dd19447dc0607bec0de22ddc9348ffe78b9f4c1a85467a9ade889c
|
|
|
CT logs (rabbitmq_amqp_client tests OTP-28 khepri)
Expired
|
832 KB |
sha256:101711e65a2799604668c350a339c7db00139475e3bb4ca6f722c30f3bd26998
|
|
|
CT logs (rabbitmq_amqp_client tests OTP-28 mnesia mixed)
Expired
|
716 KB |
sha256:fad57e14ed78cbc829c28a2456ad9b20b31121f82169cd1eb32b259e31aebf53
|
|
|
CT logs (rabbitmq_amqp_client tests OTP-28 mnesia)
Expired
|
720 KB |
sha256:0401addb570e16c8f49c14fea0a25e47d0a0f7e88b0efcd84ba6851a11160d1e
|
|
|
CT logs (rabbitmq_auth_backend_cache tests OTP-28 khepri mixed)
Expired
|
554 KB |
sha256:a4695b91adb0cb6bcd026c1086a8ff26abe724ec8bc37dc389e89d88d4ee0c10
|
|
|
CT logs (rabbitmq_auth_backend_cache tests OTP-28 khepri)
Expired
|
729 KB |
sha256:62390b8aa714d579ecec412bafe812369c1085f5d23b3bf98977f9497c0dce7e
|
|
|
CT logs (rabbitmq_auth_backend_cache tests OTP-28 mnesia mixed)
Expired
|
559 KB |
sha256:6dd2e8bd790cd2da6fbe0b3481e03240375f7d75ce1c5d46f64104290ed2df38
|
|
|
CT logs (rabbitmq_auth_backend_cache tests OTP-28 mnesia)
Expired
|
731 KB |
sha256:c7699ca80463fe70f1001cb3b7ceaebebcd34db56e04d2b1d6d78847f27bf849
|
|
|
CT logs (rabbitmq_auth_backend_http tests OTP-28 khepri mixed)
Expired
|
351 KB |
sha256:7331cb70168f6020f2c2af5061023e3b06e1874ebfc847aa55b3484af1833ad3
|
|
|
CT logs (rabbitmq_auth_backend_http tests OTP-28 khepri)
Expired
|
351 KB |
sha256:cc35f933b28f7405b444b8eebfd58fee46d0d256a7f3fc84d214e1b6e9b1240e
|
|
|
CT logs (rabbitmq_auth_backend_http tests OTP-28 mnesia mixed)
Expired
|
353 KB |
sha256:a56f27f10e0d0c0d28163846f5c9c62eac81d2f4bc4fc089d55923cb425c3c22
|
|
|
CT logs (rabbitmq_auth_backend_http tests OTP-28 mnesia)
Expired
|
352 KB |
sha256:aed303cffbd5ba17de126c6b56531f23e601f7078e8f38f601020d355ef40d4c
|
|
|
CT logs (rabbitmq_auth_backend_ldap tests OTP-28 khepri mixed)
Expired
|
398 KB |
sha256:65320a6a9d92e37112b7f6bf83c65a4e647569827b06c4ba28de33a10e6630e2
|
|
|
CT logs (rabbitmq_auth_backend_ldap tests OTP-28 khepri)
Expired
|
398 KB |
sha256:4c0772a84d1f3c073d551edbc064b01e918d5faf8d0061b4819d495df2e0daf7
|
|
|
CT logs (rabbitmq_auth_backend_ldap tests OTP-28 mnesia mixed)
Expired
|
400 KB |
sha256:5216abfec5f3b5ced7f9c9ca70c45e55c40b6dcee78b962c73a096a3dbd770df
|
|
|
CT logs (rabbitmq_auth_backend_ldap tests OTP-28 mnesia)
Expired
|
400 KB |
sha256:ffad8584b1b872160ae3dff3426fa29fe5edf2647c1cc80a7de9227d48774393
|
|
|
CT logs (rabbitmq_auth_backend_oauth2 tests OTP-28 khepri mixed)
Expired
|
2.9 MB |
sha256:68cfcbe96e01f6bba5a0f304113e55d213ab853a552c15e8506f71f9574f4b5d
|
|
|
CT logs (rabbitmq_auth_backend_oauth2 tests OTP-28 khepri)
Expired
|
2.89 MB |
sha256:93a3922f62bfd79a5ddd77b4168d32951732cd448b733f77d11fab852f0fb53c
|
|
|
CT logs (rabbitmq_auth_backend_oauth2 tests OTP-28 mnesia mixed)
Expired
|
2.69 MB |
sha256:460ac10993cdfa04fb101f99e30b9e31f67e07148406e17d72241c0dc9d31ee9
|
|
|
CT logs (rabbitmq_auth_backend_oauth2 tests OTP-28 mnesia)
Expired
|
2.68 MB |
sha256:836e2ad3121b6377632ce9587bd2ec4398550aac7741773339d3211e7bc87a20
|
|
|
CT logs (rabbitmq_auth_mechanism_ssl tests OTP-28 khepri mixed)
Expired
|
231 KB |
sha256:88daa32c0d9ab9024739308dff294cea892f12e0ce052585b18a1434ce97051a
|
|
|
CT logs (rabbitmq_auth_mechanism_ssl tests OTP-28 khepri)
Expired
|
231 KB |
sha256:c4491ee259b3008ab60593e9e48130455633560e391c89d0ab9ea7c15661263d
|
|
|
CT logs (rabbitmq_auth_mechanism_ssl tests OTP-28 mnesia mixed)
Expired
|
227 KB |
sha256:2772bcc338e593184e180b151de66addd28c0deca6a943782e3b1c73d1ff44a8
|
|
|
CT logs (rabbitmq_auth_mechanism_ssl tests OTP-28 mnesia)
Expired
|
226 KB |
sha256:440b5f9ac4f5bd77c22bcc0edec1f76803583e01c535f725d76b750aea81f8d1
|
|
|
CT logs (rabbitmq_aws tests OTP-28 khepri mixed)
Expired
|
215 KB |
sha256:cc38eca0632acb547e4171dce1d8eb5e0fbff8a5f579d6c51b7fedad988a689c
|
|
|
CT logs (rabbitmq_aws tests OTP-28 khepri)
Expired
|
215 KB |
sha256:66a89537937fd1ee1366af33e11a53493571d3f4535fd662e87d5b1ef8fa3b87
|
|
|
CT logs (rabbitmq_aws tests OTP-28 mnesia mixed)
Expired
|
216 KB |
sha256:d5eaf7238bc75a8f3384c0c6078a9fbd3d5ff6a14c4e256a252fbe007be3a038
|
|
|
CT logs (rabbitmq_aws tests OTP-28 mnesia)
Expired
|
216 KB |
sha256:e5288917de0c7a7002cb726f29ec8181b163ac4146b56e5c7a7e0e79f28a5af6
|
|
|
CT logs (rabbitmq_cli tests OTP-28 khepri mixed)
Expired
|
423 KB |
sha256:6cfabd6d0fe7c6a4cb61aaa40786810511ba99af3a3bf31a107201e171705283
|
|
|
CT logs (rabbitmq_cli tests OTP-28 khepri)
Expired
|
1.07 MB |
sha256:1e617ffa9be29de5d600020c4e082215d3fb9f0c7a84bfb38fe919b56f86995f
|
|
|
CT logs (rabbitmq_cli tests OTP-28 mnesia mixed)
Expired
|
509 KB |
sha256:559f051c088df45ad3e146ef3dc09fb0346c45fa5f17fb42e7787681790a8388
|
|
|
CT logs (rabbitmq_cli tests OTP-28 mnesia)
Expired
|
61.6 KB |
sha256:4baf49d0e5b839c65364c8be2a968fe91008ada3473fe1deb3d9c11278d5622e
|
|
|
CT logs (rabbitmq_consistent_hash_exchange tests OTP-28 khepri mixed)
Expired
|
1.41 MB |
sha256:d5fe4d497626b9a536698aed43985a0680dced062988fffcfdc014864a5c99fd
|
|
|
CT logs (rabbitmq_consistent_hash_exchange tests OTP-28 khepri)
Expired
|
1.42 MB |
sha256:4885a4d3f80b8c8768eb4dd51d1e1913df422a109b0e1aa7155f3a442e5b7d12
|
|
|
CT logs (rabbitmq_consistent_hash_exchange tests OTP-28 mnesia mixed)
Expired
|
970 KB |
sha256:d01aed380b6ee9ccf920c4408cf90604cbb8ad78c96ce5c490cc51a5bf8faa2f
|
|
|
CT logs (rabbitmq_consistent_hash_exchange tests OTP-28 mnesia)
Expired
|
965 KB |
sha256:7df44a0e1a546b3ca9239e7fea7bc533f756c4ab771516be7ec87138f504c993
|
|
|
CT logs (rabbitmq_event_exchange tests OTP-28 khepri mixed)
Expired
|
668 KB |
sha256:8f578134b5b245fd2e103f02d12aa39cdaf578f695fddd334cd73c3fdf34efc1
|
|
|
CT logs (rabbitmq_event_exchange tests OTP-28 khepri)
Expired
|
674 KB |
sha256:83ac45dc21e60c249f381161205a9e4bf22f9c4dff355ea374f185805fcf4e5c
|
|
|
CT logs (rabbitmq_event_exchange tests OTP-28 mnesia mixed)
Expired
|
559 KB |
sha256:c0d4d5791d4cbdfa3c3776b5824610f755b401150fc9f9621becceedbc54a29d
|
|
|
CT logs (rabbitmq_event_exchange tests OTP-28 mnesia)
Expired
|
558 KB |
sha256:341f73e5d547501ad868c588d8e9c7df863b16dcf13c65853faad1e6bb705718
|
|
|
CT logs (rabbitmq_exchange_federation tests OTP-28 khepri mixed)
Expired
|
2.63 MB |
sha256:1dcf87edcff09de2354a10fb871df24ca5c373abc4c7a3da1882b05ba7b974ba
|
|
|
CT logs (rabbitmq_exchange_federation tests OTP-28 khepri)
Expired
|
3.19 MB |
sha256:c7f8946b1fc48b2469995b9cc7b345f7a20970f7e6c62268376e98ea0f7d013c
|
|
|
CT logs (rabbitmq_exchange_federation tests OTP-28 mnesia mixed)
Expired
|
1.98 MB |
sha256:eeee49f29c41506fc7fadd7c936bcf465a8e30419f55231b2a19820018e8846c
|
|
|
CT logs (rabbitmq_exchange_federation tests OTP-28 mnesia)
Expired
|
2.44 MB |
sha256:bd6e18dde47655441e9f15a7fec0b88d0022958d8bec51db466a9bae134d0b0d
|
|
|
CT logs (rabbitmq_federation_common tests OTP-28 khepri mixed)
Expired
|
281 KB |
sha256:aa6ccf0b3ca0c50b54ed27e3726151be82bceea5ffcdf73a28aacf490c32a23b
|
|
|
CT logs (rabbitmq_federation_common tests OTP-28 khepri)
Expired
|
280 KB |
sha256:8d794f576cdddd8cf36a30c58df01ad063393a5a140c1f245e0d42c0aa82b1da
|
|
|
CT logs (rabbitmq_federation_common tests OTP-28 mnesia mixed)
Expired
|
278 KB |
sha256:3dd1456c3dca79b873766f2b73f58063834b21c2ba13b6f87c184d9adfd85e90
|
|
|
CT logs (rabbitmq_federation_common tests OTP-28 mnesia)
Expired
|
278 KB |
sha256:899f77461de8f64447eba8aaa009ed463867ff1911da020ec980997c32793af6
|
|
|
CT logs (rabbitmq_federation_management tests OTP-28 khepri mixed)
Expired
|
320 KB |
sha256:0410f4451ab68ef06716c68c209a4c2457e7188e3a4aa448db16f6abc6c44f4f
|
|
|
CT logs (rabbitmq_federation_management tests OTP-28 khepri)
Expired
|
318 KB |
sha256:a5f1599f26178360b3884ee113682175c2037d013ab3099f16fe689df4aef736
|
|
|
CT logs (rabbitmq_federation_management tests OTP-28 mnesia mixed)
Expired
|
266 KB |
sha256:be34b53dd83584920bb83f7af1737f3d75cc0f18588e94f4caf46467119ac146
|
|
|
CT logs (rabbitmq_federation_management tests OTP-28 mnesia)
Expired
|
266 KB |
sha256:0b293d6a14159fb43dd95e06de76b35021efcb32cb639b03b10f6abf7bcc0520
|
|
|
CT logs (rabbitmq_federation_prometheus tests OTP-28 khepri mixed)
Expired
|
265 KB |
sha256:b770ee737cb4de2d36f7759e67d7570aad52d1aba74f6e9151ff75876bc98eee
|
|
|
CT logs (rabbitmq_federation_prometheus tests OTP-28 khepri)
Expired
|
265 KB |
sha256:7444daa24e6c49755908c49b0e91cf82d6e7583e16b739f1af09db307072e6bf
|
|
|
CT logs (rabbitmq_federation_prometheus tests OTP-28 mnesia mixed)
Expired
|
260 KB |
sha256:51ad71807090c45f1d6ec7ad6105c70b755ee1d2400e1d4b748c481dd2c952ee
|
|
|
CT logs (rabbitmq_federation_prometheus tests OTP-28 mnesia)
Expired
|
260 KB |
sha256:d6f8c4b1b017d3933abeb363a0c156086a2b05ad370b83875ce5c7ab45977f48
|
|
|
CT logs (rabbitmq_jms_topic_exchange tests OTP-28 khepri mixed)
Expired
|
575 KB |
sha256:ec842fe751a32a97fe532ed940e7c4bb546c2b7fbc03bdd57263983f6165ea0d
|
|
|
CT logs (rabbitmq_jms_topic_exchange tests OTP-28 khepri)
Expired
|
575 KB |
sha256:a32745ac34f2f0ac5572c399a94572117002e81bc893361700055d7cccf326c2
|
|
|
CT logs (rabbitmq_jms_topic_exchange tests OTP-28 mnesia mixed)
Expired
|
575 KB |
sha256:8cc448bd92b5f3039a2954683ef317844b73bb0e2e18c831b840298e70fe46c9
|
|
|
CT logs (rabbitmq_jms_topic_exchange tests OTP-28 mnesia)
Expired
|
574 KB |
sha256:4a7f9453325178ad3f85d795c8d6f077e2610f82c5e99d648d367b509a4a4b05
|
|
|
CT logs (rabbitmq_management tests OTP-28 khepri mixed)
Expired
|
7.67 MB |
sha256:87f0f3168e1d6df5a7ea82fe8a8185a0eeebe9f11c3194f3855869510de26a59
|
|
|
CT logs (rabbitmq_management tests OTP-28 khepri)
Expired
|
7.76 MB |
sha256:a62ee89be74e51ac5f51c25b00f3ec0aa9738a61870cdb5a3a8e96676c409dd5
|
|
|
CT logs (rabbitmq_management tests OTP-28 mnesia mixed)
Expired
|
6.64 MB |
sha256:c22ffac03336ed2a3e50f16b1f17a9fe8319441a80fbaf56136b85454b73fe44
|
|
|
CT logs (rabbitmq_management tests OTP-28 mnesia)
Expired
|
6.69 MB |
sha256:9972362ded3c1b1c21d0c20f4c5463de6f27a5b533d51da37c293505d2756dcf
|
|
|
CT logs (rabbitmq_management_agent tests OTP-28 khepri mixed)
Expired
|
733 KB |
sha256:e98c8fe86cb985b641832d5b5173734f818e58afc79efdbc8b12cef317d27bf5
|
|
|
CT logs (rabbitmq_management_agent tests OTP-28 khepri)
Expired
|
731 KB |
sha256:2836df689ba4781e54aaffb7c4cd1ff40033e85b351c64c64ca0d9c64901f4e6
|
|
|
CT logs (rabbitmq_management_agent tests OTP-28 mnesia mixed)
Expired
|
701 KB |
sha256:a65e6a38831bbfab3673ef1114cfe4e6a17bb8482392198252b6acda13545f53
|
|
|
CT logs (rabbitmq_management_agent tests OTP-28 mnesia)
Expired
|
699 KB |
sha256:ffc6d51e3c75f62772190f9dc58098347f4a2b0a607e399db1a86aa58166bd73
|
|
|
CT logs (rabbitmq_mqtt parallel-ct-set-1 OTP-28 khepri mixed)
Expired
|
12.4 MB |
sha256:81979606d0af54797d7abebb076f9c14a284c47d961f23a11c5282db4abf62fd
|
|
|
CT logs (rabbitmq_mqtt parallel-ct-set-1 OTP-28 khepri)
Expired
|
12.5 MB |
sha256:a59cba50e67da69b0a23725e19600d7f7f672bac428e928cdab7e5132aee7823
|
|
|
CT logs (rabbitmq_mqtt parallel-ct-set-1 OTP-28 mnesia mixed)
Expired
|
10.4 MB |
sha256:497cfeb42e673b7625c3db7d5a86d078f5d90733dd5f251262e2fa98462d12ab
|
|
|
CT logs (rabbitmq_mqtt parallel-ct-set-1 OTP-28 mnesia)
Expired
|
10.4 MB |
sha256:5faaac6ad0b88597aa9910a0717a58e22e3e7de04c100dac42b177269ed58216
|
|
|
CT logs (rabbitmq_peer_discovery_aws ct-config_schema ct-unit OTP-28 khepri mixed)
Expired
|
347 KB |
sha256:93dd54d40806a8af4d0b223626e3da696658c4323786c8639b18f3e53ba0c0d2
|
|
|
CT logs (rabbitmq_peer_discovery_aws ct-config_schema ct-unit OTP-28 khepri)
Expired
|
347 KB |
sha256:12ab546150008ae5ab8c71c2060e3a888a543e6202362c8bc04972cd526b9c05
|
|
|
CT logs (rabbitmq_peer_discovery_aws ct-config_schema ct-unit OTP-28 mnesia mixed)
Expired
|
349 KB |
sha256:cb7f5382a06719c4a12f4adb40fb554851d8c647c3a4dc43168a50224091bb4c
|
|
|
CT logs (rabbitmq_peer_discovery_aws ct-config_schema ct-unit OTP-28 mnesia)
Expired
|
349 KB |
sha256:c70c39ada48943affa98c7b905150e18aab4017ada9bf731836cc2ea0adb2cf3
|
|
|
CT logs (rabbitmq_peer_discovery_common tests OTP-28 khepri mixed)
Expired
|
879 KB |
sha256:c09794a8826117fc2d303a6fd1f0f78de5e6e5126c68eb9a377cf5ed1f71c6ad
|
|
|
CT logs (rabbitmq_peer_discovery_common tests OTP-28 khepri)
Expired
|
879 KB |
sha256:b2681e50461b5c7a3c37a6793c4de578fab4acd1d5b4359a783572e204b2e54a
|
|
|
CT logs (rabbitmq_peer_discovery_common tests OTP-28 mnesia mixed)
Expired
|
872 KB |
sha256:b8cf9f28f5dae270743f781f9dadb30ee9b2249aa7aa4dbbd73c5dedc8d9c7ed
|
|
|
CT logs (rabbitmq_peer_discovery_common tests OTP-28 mnesia)
Expired
|
864 KB |
sha256:07bf87501129cdf7400499d4952852defa2299535e0437854dfa2b991241282a
|
|
|
CT logs (rabbitmq_peer_discovery_consul tests OTP-28 khepri mixed)
Expired
|
898 KB |
sha256:d1f6f7512a7a4152c774ac430fc01e7897a8863d4c38c2724222297c1b9d750c
|
|
|
CT logs (rabbitmq_peer_discovery_consul tests OTP-28 khepri)
Expired
|
1.08 MB |
sha256:c882c75f611b4243e329bb634f18dcf538661eb796de725b36121ceadc182d4a
|
|
|
CT logs (rabbitmq_peer_discovery_consul tests OTP-28 mnesia mixed)
Expired
|
908 KB |
sha256:87b373347e78610ef4d0334e1b6e07f205d2d9ddaaafa1ae174f4f62b66aec06
|
|
|
CT logs (rabbitmq_peer_discovery_consul tests OTP-28 mnesia)
Expired
|
1.04 MB |
sha256:b557e84690c78b3ce1a718fe002dbf09b364f72f08d00a8695e587699ed60f83
|
|
|
CT logs (rabbitmq_peer_discovery_etcd tests OTP-28 khepri mixed)
Expired
|
852 KB |
sha256:d6e80e5af7305567e6f3296fd23a47f13387e57ed0ef16f9165e3b089e8aaab9
|
|
|
CT logs (rabbitmq_peer_discovery_etcd tests OTP-28 khepri)
Expired
|
1.04 MB |
sha256:cd17721dd2d09794c3be1f15ade454f4ae77f6a9fe2466e44b26c60f38f0f2c3
|
|
|
CT logs (rabbitmq_peer_discovery_etcd tests OTP-28 mnesia mixed)
Expired
|
868 KB |
sha256:f206cf462b15e2b5b91f7850a4c59f82490f1cee8181eafc3773d74b25a6f7e1
|
|
|
CT logs (rabbitmq_peer_discovery_etcd tests OTP-28 mnesia)
Expired
|
1010 KB |
sha256:13e776653ef075464d32dee308094a6977f5684e13dcaa36de9bbebb766b1bc1
|
|
|
CT logs (rabbitmq_peer_discovery_k8s tests OTP-28 khepri mixed)
Expired
|
277 KB |
sha256:515691eecb7ba93722856d2219b0a8eac4b7b245b0bdbd3e0b2ff08bc1417295
|
|
|
CT logs (rabbitmq_peer_discovery_k8s tests OTP-28 khepri)
Expired
|
276 KB |
sha256:3cf5ca0ad0ada3c533c901804f190a84fb270b4c5842e0b474e0b67454acf92d
|
|
|
CT logs (rabbitmq_peer_discovery_k8s tests OTP-28 mnesia mixed)
Expired
|
279 KB |
sha256:7d6427756f30ddc9c91ed7500bc272e52a9221af5b42e0eabae240fe3978ca07
|
|
|
CT logs (rabbitmq_peer_discovery_k8s tests OTP-28 mnesia)
Expired
|
279 KB |
sha256:993ad4b9414613766487a4e3d1404e291335cd24790127a7fd5a62090a5af330
|
|
|
CT logs (rabbitmq_prometheus tests OTP-28 khepri mixed)
Expired
|
1.93 MB |
sha256:6ab6cbf33ae12a22b43cf81d0108aa8c29dfbfceaaf7fd1b70985153d8474068
|
|
|
CT logs (rabbitmq_prometheus tests OTP-28 khepri)
Expired
|
1.93 MB |
sha256:11592b7e6fb203649e227164e5ed358bc2a905e65b9853b78cd62200dcf6d767
|
|
|
CT logs (rabbitmq_prometheus tests OTP-28 mnesia mixed)
Expired
|
1.93 MB |
sha256:306d26295e4fb181d38333be7376d725f3cde9fa8e9d40a0e951beab982f7fad
|
|
|
CT logs (rabbitmq_prometheus tests OTP-28 mnesia)
Expired
|
1.93 MB |
sha256:2fd9dc62eaca8cff54f9f228b2323920c0e956d72bf3552e6c16d464b2e543ca
|
|
|
CT logs (rabbitmq_queue_federation tests OTP-28 khepri mixed)
Expired
|
1.75 MB |
sha256:58d876198cf1b2e0750aca3295102a1b1ad84b81fcdd489ccae8829703f1e549
|
|
|
CT logs (rabbitmq_queue_federation tests OTP-28 khepri)
Expired
|
2.25 MB |
sha256:82601c7ee1d1236915e842cd32cb504782274e2a934d353ef352f93ede6c3744
|
|
|
CT logs (rabbitmq_queue_federation tests OTP-28 mnesia mixed)
Expired
|
1.57 MB |
sha256:20f2c620731356f94cee3509aabe6f7147545fe6f3bf1ed74444a3a92c64a734
|
|
|
CT logs (rabbitmq_queue_federation tests OTP-28 mnesia)
Expired
|
2.06 MB |
sha256:6ed424fbf509af0a22563a38c501dc0da7c15d101ea511760db51c61f49dfaf6
|
|
|
CT logs (rabbitmq_recent_history_exchange tests OTP-28 khepri mixed)
Expired
|
698 KB |
sha256:b78323e10e22a7049e0abeae7d92976ce6b86b5271e47fa355e168fa5f539cf6
|
|
|
CT logs (rabbitmq_recent_history_exchange tests OTP-28 khepri)
Expired
|
693 KB |
sha256:b5632e0c6c9dc35fc5700f10237be492e9c043cafe56c18350343a032356f9b7
|
|
|
CT logs (rabbitmq_recent_history_exchange tests OTP-28 mnesia mixed)
Expired
|
524 KB |
sha256:44b07b66ec5f0b05948e45b3155d6b08c38c1e152ccc4f0600554e5ceffe4c1c
|
|
|
CT logs (rabbitmq_recent_history_exchange tests OTP-28 mnesia)
Expired
|
516 KB |
sha256:6445f9047ebee2117581af97cc54918cb296e301e3d228c3226eed1f37f68885
|
|
|
CT logs (rabbitmq_sharding tests OTP-28 khepri mixed)
Expired
|
999 KB |
sha256:b9f910fa459f6b552f9c48446b66747e3fed420191a83458dff3432ea6bd42de
|
|
|
CT logs (rabbitmq_sharding tests OTP-28 khepri)
Expired
|
953 KB |
sha256:efbee21f7e46e3b5aef789b1bd4882f0bd26003abd42fc8ad76679169ce9f870
|
|
|
CT logs (rabbitmq_sharding tests OTP-28 mnesia mixed)
Expired
|
527 KB |
sha256:d798412779a25ac90fca528a356b42b597b8f7789ac4b192112e0cde539f940d
|
|
|
CT logs (rabbitmq_sharding tests OTP-28 mnesia)
Expired
|
522 KB |
sha256:452c98d8521f4b291029364a0cd959dff520455f7f54334c6417cec12ae3b9f8
|
|
|
CT logs (rabbitmq_shovel tests OTP-28 khepri mixed)
Expired
|
18.7 MB |
sha256:bbfd1b89cb39b85cdadbb16c76f70a036054402c105afa74a5bed1a8effdce64
|
|
|
CT logs (rabbitmq_shovel tests OTP-28 khepri)
Expired
|
18.6 MB |
sha256:b92f1c8a38fddd615fe2f183e29052a9a362d2d43129ee6ce1c43acb988f4a82
|
|
|
CT logs (rabbitmq_shovel tests OTP-28 mnesia mixed)
Expired
|
15.3 MB |
sha256:ce09f9396ed53418533f191c2e74eaa4a4536f741b3c2a6e15d212848ff12413
|
|
|
CT logs (rabbitmq_shovel tests OTP-28 mnesia)
Expired
|
15.2 MB |
sha256:4261da12a1bb4f04a4d45762d83425d5b963790b75889d20e45145d199a9f777
|
|
|
CT logs (rabbitmq_shovel_management tests OTP-28 khepri mixed)
Expired
|
430 KB |
sha256:363edbc84c94061303a08656de757bf3b759fc74e2eb1432ba9b749a443a644e
|
|
|
CT logs (rabbitmq_shovel_management tests OTP-28 khepri)
Expired
|
430 KB |
sha256:4f5914af3588b6cf0451169df65560630114b1751b52395f96dcc80dfec2a663
|
|
|
CT logs (rabbitmq_shovel_management tests OTP-28 mnesia mixed)
Expired
|
403 KB |
sha256:190f85060725d6acf7132358e390ecebaa5a48b163902f61b2297737981dfe71
|
|
|
CT logs (rabbitmq_shovel_management tests OTP-28 mnesia)
Expired
|
405 KB |
sha256:0206c9877b907af1b5b10f9399feada639b333b10305100a162ab4cd267833bc
|
|
|
CT logs (rabbitmq_shovel_prometheus tests OTP-28 khepri mixed)
Expired
|
258 KB |
sha256:2ee530a5a67531050a311a9fdd4d38a5ac8edf547456adbf1beac6a8a87cdf27
|
|
|
CT logs (rabbitmq_shovel_prometheus tests OTP-28 khepri)
Expired
|
258 KB |
sha256:c13767594ec37bc486796d555ed975f4a94947777343cb052a94c392076e0766
|
|
|
CT logs (rabbitmq_shovel_prometheus tests OTP-28 mnesia mixed)
Expired
|
257 KB |
sha256:fb10d69db390f2349da788cb7f0b29255d2898807efd26780371880636d67dce
|
|
|
CT logs (rabbitmq_shovel_prometheus tests OTP-28 mnesia)
Expired
|
257 KB |
sha256:0268f6c5a91aa0b6da47513b3e473e2631c5648ada0d0a89e8f7f9592cbabb93
|
|
|
CT logs (rabbitmq_stomp tests OTP-28 khepri mixed)
Expired
|
1.56 MB |
sha256:61ed6ab6fba9a5b449c07c55f4b58ff0c18623de23c340a16692e5bb2e661457
|
|
|
CT logs (rabbitmq_stomp tests OTP-28 khepri)
Expired
|
1.56 MB |
sha256:0b87d9105f9c6b94f8581b8d024860be0eb75b6c69354099f62bf0b32300279e
|
|
|
CT logs (rabbitmq_stomp tests OTP-28 mnesia mixed)
Expired
|
1.45 MB |
sha256:b39d67c8d4168e4ddccc1ae63c33466ccb2763612c0b4ff7824c19863cdb0f0a
|
|
|
CT logs (rabbitmq_stomp tests OTP-28 mnesia)
Expired
|
1.44 MB |
sha256:83e664ad5f8937b82846c4f988d454c3d7eecc369b7005cdc0672beee1f2a9fe
|
|
|
CT logs (rabbitmq_stream tests OTP-28 khepri mixed)
Expired
|
576 KB |
sha256:09cf28644adbc120a09e32a011eef0920e393970223a99022fcc486f10b6e93a
|
|
|
CT logs (rabbitmq_stream tests OTP-28 khepri)
Expired
|
3.07 MB |
sha256:b031c66e9502dd1e2dcf0d3eb04c6552831db9927acdb6370c11cdfc13d6fd1f
|
|
|
CT logs (rabbitmq_stream tests OTP-28 mnesia mixed)
Expired
|
573 KB |
sha256:22878255655ad3d4f5a7b47af99990c4f97c3900ba51954481b161a22cb7d905
|
|
|
CT logs (rabbitmq_stream tests OTP-28 mnesia)
Expired
|
2.51 MB |
sha256:8b423aae24b93afd978c27d611aaa56607e66633886078f1ec33e9f13cdbae8c
|
|
|
CT logs (rabbitmq_stream_common tests OTP-28 khepri mixed)
Expired
|
130 KB |
sha256:51e153bb7f07e76fe2f9874346a16c7c25096ef4c24901b8272b016178f0d530
|
|
|
CT logs (rabbitmq_stream_common tests OTP-28 khepri)
Expired
|
130 KB |
sha256:e8aa350be7dc5840abf7085f9f253287073c26c412ca34a0406404eb46593315
|
|
|
CT logs (rabbitmq_stream_common tests OTP-28 mnesia mixed)
Expired
|
130 KB |
sha256:2e23b6786179e310abccadecfa5021ff8ab51c8ec5123665d9310b90dc0c1ace
|
|
|
CT logs (rabbitmq_stream_common tests OTP-28 mnesia)
Expired
|
130 KB |
sha256:b1150be2dc697e9f963c91697b686afe1278374a99fa14f3987fe7a5aff321a0
|
|
|
CT logs (rabbitmq_stream_management tests OTP-28 khepri mixed)
Expired
|
120 KB |
sha256:cdac55d1dacc4802a9c28260834fdc0c3fb98868830f0c360c178f3adb6c530b
|
|
|
CT logs (rabbitmq_stream_management tests OTP-28 khepri)
Expired
|
336 KB |
sha256:dc8f880314bac70ee03931559c679cdcc84dff07de445bdde247677f243b49bb
|
|
|
CT logs (rabbitmq_stream_management tests OTP-28 mnesia mixed)
Expired
|
120 KB |
sha256:8d5aac693bfadcd97014ef572a8516c369b0b329601fe4e44ed5f29590a8e9f8
|
|
|
CT logs (rabbitmq_stream_management tests OTP-28 mnesia)
Expired
|
321 KB |
sha256:da74b0b6cefbb3f1aa468cee06417e3752bf9363b6b497b2b55b68ca0ae3aa3a
|
|
|
CT logs (rabbitmq_tracing tests OTP-28 khepri mixed)
Expired
|
362 KB |
sha256:2b5088cd3a651aafe9ac6b59208342ad58e55e19a3c862ec2957f95237aaeee0
|
|
|
CT logs (rabbitmq_tracing tests OTP-28 khepri)
Expired
|
362 KB |
sha256:6ca7218c569a6e4fa99cd599f11437063a9cfa85d91782a3580cea131ffe85a6
|
|
|
CT logs (rabbitmq_tracing tests OTP-28 mnesia mixed)
Expired
|
359 KB |
sha256:dc6a384b64acbcf9f6076f014f17adf578031e4b7b84a3994b27d1e3285bc877
|
|
|
CT logs (rabbitmq_tracing tests OTP-28 mnesia)
Expired
|
359 KB |
sha256:7e00f29fc28d909ce7a1d8945c96f46b2a3b9f7ce14726d7eff1a8a7371a4363
|
|
|
CT logs (rabbitmq_trust_store tests OTP-28 khepri mixed)
Expired
|
575 KB |
sha256:1a59c3c6d61cabc78e7ff052f3e67a215822ad1c5a016606fdacf1eb53b99007
|
|
|
CT logs (rabbitmq_trust_store tests OTP-28 khepri)
Expired
|
575 KB |
sha256:0dcb64b29f17d265defa8e03bee9e03f7bc327abe67f462cd7a45b3446f3ba12
|
|
|
CT logs (rabbitmq_trust_store tests OTP-28 mnesia mixed)
Expired
|
566 KB |
sha256:596c711dd83ca552979477fdb2aba55fd7dc9697741e382f5770eceeed817ca0
|
|
|
CT logs (rabbitmq_trust_store tests OTP-28 mnesia)
Expired
|
565 KB |
sha256:73eed517882685f975fb0aa3f968789f2e7b9ae3e4d7178cd4a074f720c8a0b0
|
|
|
CT logs (rabbitmq_web_dispatch tests OTP-28 khepri mixed)
Expired
|
387 KB |
sha256:4fbe26722c8876afb6a11099c9ed4ba9a79120d441e772ceac6887d946db124f
|
|
|
CT logs (rabbitmq_web_dispatch tests OTP-28 khepri)
Expired
|
386 KB |
sha256:a1fc89cdf7cb08bca2f3d0df98d2eed50130b000078e979865dadd59178054b8
|
|
|
CT logs (rabbitmq_web_dispatch tests OTP-28 mnesia mixed)
Expired
|
391 KB |
sha256:c43f599332041b19a758e4587447285bae84dac994cc1f19a521067bc35ea6b8
|
|
|
CT logs (rabbitmq_web_dispatch tests OTP-28 mnesia)
Expired
|
390 KB |
sha256:3e3ac118571abd232ac1fcfe2cef6eaea8c2fe2af6adc9d95cb2211af7543951
|
|
|
CT logs (rabbitmq_web_mqtt tests OTP-28 khepri mixed)
Expired
|
3.91 MB |
sha256:a01646ed312a166699c0196f69e40feb085415a94a631b811428255cbace8b0c
|
|
|
CT logs (rabbitmq_web_mqtt tests OTP-28 khepri)
Expired
|
3.92 MB |
sha256:daa9c1255bcf6d6cb981f268b530dafb0ea4c3f79b19b3905ea560a1e42972d5
|
|
|
CT logs (rabbitmq_web_mqtt tests OTP-28 mnesia mixed)
Expired
|
3.03 MB |
sha256:4c3e22775dc583ae36742917ca26e3def896a5992ca827adc1c260748eae16a7
|
|
|
CT logs (rabbitmq_web_mqtt tests OTP-28 mnesia)
Expired
|
3.05 MB |
sha256:ea0803f2cbac930b49b0fac4af123cd8566edcb3b94b4cba185765cd82c9c9ac
|
|
|
CT logs (rabbitmq_web_stomp tests OTP-28 khepri mixed)
Expired
|
987 KB |
sha256:ccd94b0f6e7f0f52fe2d4956bdf8b46fb4cddb2045d4fe67e71bdd0a06540754
|
|
|
CT logs (rabbitmq_web_stomp tests OTP-28 khepri)
Expired
|
987 KB |
sha256:015f794c1098d0e6cd511b2398d7511ee00acd90403c4d3b8275adba33792e49
|
|
|
CT logs (rabbitmq_web_stomp tests OTP-28 mnesia mixed)
Expired
|
963 KB |
sha256:cea3cd96be04324bc2d8ce9ad6d0e260f92f2e993da4c79701a9115df86687a6
|
|
|
CT logs (rabbitmq_web_stomp tests OTP-28 mnesia)
Expired
|
963 KB |
sha256:d030ed9d33deab96ac8af7cfacde04fd6b9c39bf37d5ca5f3cd6f3ba86c57d09
|
|