Skip to content
Continuous Integration

[RFC][0.6.x] Helpers #528

Sign in to view logs

[RFC][0.6.x] Helpers

[RFC][0.6.x] Helpers #528

Triggered via pull request March 31, 2026 06:08
@WyriHaximusWyriHaximus
synchronize #178
0.6.x-helpers
Status Cancelled
Total duration 10m 19s
Artifacts –

ci.yml

on: pull_request
Supported Versions Matrix
4s
Supported Versions Matrix
Matrix: static-anylsis
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

246 errors and 128 warnings
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: highest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: locked; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: locked; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: locked; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: highest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: highest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: highest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: highest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: highest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: highest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: highest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: locked; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: highest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: highest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: highest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: highest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: highest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: highest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: locked; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: locked; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: locked; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: highest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: highest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: highest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: highest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: highest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: locked; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: highest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: highest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: highest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: locked; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: highest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: locked; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: highest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.4 against RabbitMQ 4.1 (Composer: lowest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: highest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: highest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.4 against RabbitMQ 4.1 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: lowest; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: highest; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: locked; TLS: yes)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: highest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: locked; TLS: client)
Process completed with exit code 2.
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: lowest; TLS: no)
Process completed with exit code 2.
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: lowest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: lowest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: lowest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3 (Composer: lowest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.9 (Composer: lowest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3 (Composer: lowest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.9 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.9 (Composer: lowest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4.1 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.9 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: lowest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.9 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3 (Composer: lowest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: lowest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4.1 (Composer: lowest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4.1 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.9 (Composer: lowest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4.1 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.9 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.9 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4.1 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3 (Composer: lowest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.8 (Composer: lowest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4 (Composer: lowest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.9 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3 (Composer: lowest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4.1 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.9 (Composer: lowest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4.1 (Composer: lowest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4.1 (Composer: lowest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.8 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4.1 (Composer: lowest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4.1 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.8 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.8 (Composer: lowest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.9 (Composer: lowest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4 (Composer: lowest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.8 (Composer: lowest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4 (Composer: lowest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4.1 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.8 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3 (Composer: lowest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.9 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.8 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.8 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.9 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.9 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.9 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4.1 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.9 (Composer: lowest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4.1 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.9 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4.1 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4.1 (Composer: locked; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 4.1 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.8 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.5 against RabbitMQ 3.9 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: highest; TLS: yes)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: locked; TLS: yes)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: lowest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: lowest; TLS: yes)
The operation was canceled.
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: lowest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: lowest; TLS: yes)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: highest; TLS: no)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: lowest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: highest; TLS: no)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: lowest; TLS: client)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: locked; TLS: yes)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: highest; TLS: client)
The operation was canceled.
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: lowest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: lowest; TLS: yes)
The operation was canceled.
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: highest; TLS: client)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: locked; TLS: client)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: locked; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: locked; TLS: yes)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: lowest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: highest; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: lowest; TLS: client)
The operation was canceled.
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: highest; TLS: client)
The operation was canceled.
Run Tests on PHP 8.4 against RabbitMQ 3 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: highest; TLS: yes)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3 (Composer: locked; TLS: client)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: highest; TLS: yes)
The operation was canceled.
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: locked; TLS: client)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: locked; TLS: client)
The operation was canceled.
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: locked; TLS: client)
The operation was canceled.
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: locked; TLS: client)
The run was canceled by @WyriHaximus.
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: locked; TLS: client)
The operation was canceled.
Continuous Integration
The run was canceled by @WyriHaximus.
Supported Versions Matrix
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, WyriHaximus/github-action-composer-php-versions-in-range@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run static analysis on PHP 8.1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run static analysis on PHP 8.5
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: locked; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: locked; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: locked; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: highest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: highest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: highest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: locked; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: highest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: locked; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: locked; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: locked; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: highest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4.1 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: highest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: locked; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.8 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: locked; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.9 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 3.9 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: locked; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.4 against RabbitMQ 4.1 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: highest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.4 against RabbitMQ 4.1 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4.1 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 4 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: lowest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: highest; TLS: no)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.9 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3 (Composer: highest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: lowest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.2 against RabbitMQ 3.8 (Composer: highest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: locked; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: lowest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.1 against RabbitMQ 4 (Composer: highest; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.4 against RabbitMQ 3 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 4.1 (Composer: highest; TLS: yes)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.4 against RabbitMQ 3.8 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 3.8 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.3 against RabbitMQ 4 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Run Tests on PHP 8.4 against RabbitMQ 4 (Composer: locked; TLS: client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3, actions/checkout@v4, ifaxity/wait-on-action@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/