Skip to content
Testing

ci: centralize test matrix, add Laravel 13, simplify PHP versions #2

Sign in to view logs

ci: centralize test matrix, add Laravel 13, simplify PHP versions

ci: centralize test matrix, add Laravel 13, simplify PHP versions #2

Triggered via push March 14, 2026 18:16
@phillipficklphillipfickl
pushed d3869f3
fix/simplify-ci-matrix
Status Failure
Total duration 21m 41s
Artifacts –

tests.yml

on: push
Generate Matrix
2s
Generate Matrix
MariaDB 10.10  /  Filter Matrix
2s
MariaDB 10.10 / Filter Matrix
MariaDB 10.3  /  Filter Matrix
2s
MariaDB 10.3 / Filter Matrix
MariaDB 10.4  /  Filter Matrix
2s
MariaDB 10.4 / Filter Matrix
MariaDB 10.5  /  Filter Matrix
3s
MariaDB 10.5 / Filter Matrix
MariaDB 10.6  /  Filter Matrix
2s
MariaDB 10.6 / Filter Matrix
MariaDB 10.7  /  Filter Matrix
4s
MariaDB 10.7 / Filter Matrix
MariaDB 10.8  /  Filter Matrix
3s
MariaDB 10.8 / Filter Matrix
MariaDB 10.9  /  Filter Matrix
2s
MariaDB 10.9 / Filter Matrix
MariaDB 11.0  /  Filter Matrix
2s
MariaDB 11.0 / Filter Matrix
MariaDB 11.1  /  Filter Matrix
4s
MariaDB 11.1 / Filter Matrix
MariaDB 11.2  /  Filter Matrix
2s
MariaDB 11.2 / Filter Matrix
MariaDB 11.3  /  Filter Matrix
3s
MariaDB 11.3 / Filter Matrix
MariaDB 11.2  /  Filter Matrix
2s
MariaDB 11.2 / Filter Matrix
Matrix: MySQL 5.7 / test
Matrix: MySQL 8.0 / test
Matrix: MySQL 8.1 / test
Matrix: MySQL 8.2 / test
Matrix: MySQL 8.3 / test
Matrix: MySQL 8.4 / test
Matrix: PostgreSQL 10 / test
Matrix: PostgreSQL 11 / test
Matrix: PostgreSQL 12 / test
Matrix: PostgreSQL 13 / test
Matrix: PostgreSQL 14 / test
Matrix: PostgreSQL 15 / test
Matrix: PostgreSQL 16 / test
Matrix: SQLite / test
Matrix: Microsoft SQL Server 2017 (GA) / test
Matrix: Microsoft SQL Server 2017 (Latest) / test
Matrix: Microsoft SQL Server 2019 (GA) / test
Matrix: Microsoft SQL Server 2019 (Latest) / test
Matrix: Microsoft SQL Server 2022 (GA) / test
Matrix: Microsoft SQL Server 2022 (Latest) / test
Matrix: MariaDB 10.10 / test
Matrix: MariaDB 10.3 / test
Matrix: MariaDB 10.4 / test
Matrix: MariaDB 10.5 / test
Matrix: MariaDB 10.6 / test
Matrix: MariaDB 10.7 / test
Matrix: MariaDB 10.8 / test
Matrix: MariaDB 10.9 / test
Matrix: MariaDB 11.0 / test
Matrix: MariaDB 11.1 / test
Matrix: MariaDB 11.2 / test
Matrix: MariaDB 11.3 / test
Matrix: MariaDB 11.2 / test
Fit to window
Zoom out
Zoom in

Annotations

360 errors and 547 warnings
Microsoft SQL Server 2022 (GA) / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2022 (GA) / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (Latest) / P8.1 - L10.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.1 - L10.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
Microsoft SQL Server 2022 (GA) / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (Latest) / P8.2 - L12.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.2 - L12.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
Microsoft SQL Server 2022 (GA) / P8.4 - L10.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2022 (GA) / P8.4 - L12.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.4 - L12.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.1 - L10.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.2 - L11.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.2 - L12.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.4 - L10.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.2 - L12.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.2 - L11.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.4 - L11.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.4 - L11.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2022 (GA) / P8.1 - L10.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2019 (Latest) / P8.4 - L13.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.4 - L13.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
PostgreSQL 12 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 12 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 12 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 12 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (Latest) / P8.4 - L12.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.4 - L12.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
PostgreSQL 12 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 12 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (Latest) / P8.4 - L11.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.4 - L11.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
Microsoft SQL Server 2019 (Latest) / P8.4 - L13.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.4 - L13.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
Microsoft SQL Server 2019 (Latest) / P8.2 - L11.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.2 - L11.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
Microsoft SQL Server 2019 (Latest) / P8.3 - L13.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.3 - L13.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
Microsoft SQL Server 2019 (Latest) / P8.3 - L13.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.3 - L13.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
Microsoft SQL Server 2019 (Latest) / P8.2 - L12.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.2 - L12.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
Microsoft SQL Server 2019 (Latest) / P8.4 - L10.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.4 - L10.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
Microsoft SQL Server 2019 (Latest) / P8.4 - L11.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.4 - L11.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
Microsoft SQL Server 2019 (Latest) / P8.1 - L10.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.1 - L10.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
Microsoft SQL Server 2019 (Latest) / P8.4 - L12.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.4 - L12.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
MySQL 8.0 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.0 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
SQLite / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
SQLite / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (Latest) / P8.4 - L10.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.4 - L10.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
MySQL 8.1 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 8.1 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MySQL 8.1 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.1 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2022 (Latest) / P8.1 - L10.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.1 - L10.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
SQLite / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
SQLite / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MySQL 8.1 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.1 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 12 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 12 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MySQL 8.1 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 8.1 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 11 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 11 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 11 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 11 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
SQLite / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
SQLite / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
SQLite / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
SQLite / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2022 (Latest) / P8.4 - L10.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.4 - L10.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
Microsoft SQL Server 2022 (Latest) / P8.2 - L11.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.2 - L11.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
PostgreSQL 11 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 11 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2022 (Latest) / P8.1 - L10.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.1 - L10.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
Microsoft SQL Server 2022 (Latest) / P8.4 - L11.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.4 - L11.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
Microsoft SQL Server 2022 (Latest) / P8.4 - L13.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.4 - L13.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
Microsoft SQL Server 2022 (Latest) / P8.2 - L12.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.2 - L12.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
MySQL 8.0 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.0 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MySQL 8.0 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 8.0 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2022 (Latest) / P8.4 - L10.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.4 - L10.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
Microsoft SQL Server 2022 (Latest) / P8.3 - L13.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.3 - L13.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
Microsoft SQL Server 2022 (Latest) / P8.4 - L12.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.4 - L12.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
MySQL 5.7 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 5.7 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2022 (Latest) / P8.2 - L11.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.2 - L11.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
Microsoft SQL Server 2022 (Latest) / P8.3 - L13.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.3 - L13.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
Microsoft SQL Server 2022 (Latest) / P8.2 - L12.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.2 - L12.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
PostgreSQL 15 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 15 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 15 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 15 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2022 (Latest) / P8.4 - L12.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.4 - L12.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
PostgreSQL 15 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 15 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (Latest) / P8.2 - L11.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2019 (Latest) / P8.2 - L11.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2019-latest
MySQL 8.4 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.4 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (GA) / P8.4 - L12.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2017 (GA) / P8.4 - L10.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2017 (GA) / P8.2 - L12.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2022 (Latest) / P8.4 - L11.* - prefer-stable
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.4 - L11.* - prefer-stable
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
Microsoft SQL Server 2017 (GA) / P8.2 - L11.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2017 (GA) / P8.4 - L11.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 15 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 15 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (GA) / P8.2 - L11.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 11 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 11 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (GA) / P8.1 - L10.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2017 (GA) / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2017 (GA) / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (GA) / P8.4 - L10.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2017 (GA) / P8.4 - L12.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2017 (GA) / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2017 (GA) / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MySQL 8.4 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 8.4 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (GA) / P8.2 - L12.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.4 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.4 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 13 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 13 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (GA) / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2017 (GA) / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (GA) / P8.4 - L11.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2017 (GA) / P8.1 - L10.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2022 (Latest) / P8.4 - L13.* - prefer-lowest
One or more containers failed to start.
Microsoft SQL Server 2022 (Latest) / P8.4 - L13.* - prefer-lowest
Failed to initialize container mcr.microsoft.com/mssql/server:2022-latest
MySQL 8.0 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 8.0 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MySQL 5.7 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 5.7 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (GA) / P8.2 - L11.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.2 - L12.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (GA) / P8.4 - L11.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.4 - L10.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.1 - L10.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 13 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 13 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 13 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 13 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MySQL 5.7 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 5.7 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 13 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 13 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MySQL 5.7 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 5.7 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (GA) / P8.4 - L11.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.4 - L12.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (GA) / P8.2 - L11.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (GA) / P8.4 - L10.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2019 (GA) / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.3 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.3 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.3 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.3 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.3 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.3 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (GA) / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2017 (GA) / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (GA) / P8.4 - L12.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 10 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 10 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 10 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 10 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (GA) / P8.1 - L10.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2017 (Latest) / P8.4 - L11.* - prefer-stable
Process completed with exit code 2.
MySQL 8.2 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.2 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2017 (Latest) / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.3 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.3 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2019 (GA) / P8.2 - L12.* - prefer-stable
Process completed with exit code 2.
MySQL 8.2 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.2 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2017 (Latest) / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 10 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 10 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 10 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 10 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.4 - L10.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.7 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.7 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.4 - L12.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 14 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 14 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 14 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 14 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.7 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.7 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2017 (Latest) / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.7 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.7 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.4 - L12.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2017 (Latest) / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2017 (Latest) / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.1 - L10.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.2 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 8.2 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.4 - L11.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 14 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 14 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.2 - L11.* - prefer-lowest
Process completed with exit code 2.
Microsoft SQL Server 2017 (Latest) / P8.2 - L12.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.2 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 8.2 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.2 - L12.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.7 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.7 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.4 - L10.* - prefer-stable
Process completed with exit code 2.
MySQL 8.4 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 8.4 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 14 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 14 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MySQL 8.3 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.3 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2017 (Latest) / P8.2 - L11.* - prefer-stable
Process completed with exit code 2.
Microsoft SQL Server 2017 (Latest) / P8.1 - L10.* - prefer-stable
Process completed with exit code 2.
MySQL 8.3 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MySQL 8.3 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MySQL 8.3 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 8.3 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MySQL 8.3 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MySQL 8.3 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 16 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 16 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.9 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.9 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.9 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.9 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.9 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.9 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 16 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 16 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 16 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
PostgreSQL 16 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.9 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.9 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.5 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.5 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
PostgreSQL 16 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
PostgreSQL 16 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.5 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.5 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.5 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.5 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.5 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.5 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.8 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.8 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.8 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.8 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.8 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.8 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.8 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.8 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.0 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 11.0 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.0 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 11.0 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.6 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.6 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.0 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 11.0 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.0 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 11.0 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.6 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.6 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.6 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.6 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.6 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.6 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.4 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.4 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.4 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.4 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.4 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.4 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.10 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.10 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.10 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.10 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.4 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.4 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.10 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 10.10 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 10.10 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 10.10 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.2 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 11.2 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.2 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 11.2 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.2 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 11.2 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.2 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 11.2 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.3 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 11.3 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.3 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 11.3 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.2 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 11.2 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.3 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 11.3 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.3 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 11.3 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.2 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 11.2 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.2 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 11.2 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.2 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 11.2 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.1 / P8.4 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 11.1 / P8.4 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.1 / P8.3 - L13.* - prefer-lowest
Process completed with exit code 2.
MariaDB 11.1 / P8.3 - L13.* - prefer-lowest
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.1 / P8.4 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 11.1 / P8.4 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
MariaDB 11.1 / P8.3 - L13.* - prefer-stable
Process completed with exit code 2.
MariaDB 11.1 / P8.3 - L13.* - prefer-stable
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires pestphp/pest-plugin-laravel ^2.2.0|^3.0.0 -> satisfiable by pestphp/pest-plugin-laravel[v2.2.0, v2.3.0, v2.4.0, 2.x-dev, v3.0.0, v3.1.0, v3.2.0, 3.x-dev]. - pestphp/pest-plugin-laravel v2.2.0 requires laravel/framework ^10.18.0|^11.0 -> found laravel/framework[v10.18.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v2.3.0 requires laravel/framework ^10.44.0|^11.0 -> found laravel/framework[v10.44.0, ..., 10.x-dev, v11.0.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel[v2.4.0, ..., 2.x-dev] require laravel/framework ^10.48.9|^11.5.0 -> found laravel/framework[v10.48.9, ..., 10.x-dev, v11.5.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.0.0 requires laravel/framework ^11.22.0 -> found laravel/framework[v11.22.0, ..., 11.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.1.0 requires laravel/framework ^11.39.1|^12.0.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.0.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel v3.2.0 requires laravel/framework ^11.39.1|^12.9.2 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.9.2, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*). - pestphp/pest-plugin-laravel 3.x-dev requires laravel/framework ^11.39.1|^12.25.0 -> found laravel/framework[v11.39.1, ..., 11.x-dev, v12.25.0, ..., 12.x-dev] but it conflicts with your root composer.json require (13.*).
Microsoft SQL Server 2022 (GA) / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
Microsoft SQL Server 2022 (GA) / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
Microsoft SQL Server 2022 (GA) / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
Microsoft SQL Server 2022 (GA) / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2022 (GA) / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 12 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.1 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.1 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 15 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 15 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
SQLite / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.1 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 12 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
SQLite / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 15 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 12 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 12 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
SQLite / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 11 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 11 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 5.7 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 15 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.1 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.0 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
Microsoft SQL Server 2017 (GA) / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 15 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 15 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.4 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 13 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 13 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 10 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 11 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 13 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.4 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.4 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.0 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.0 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
Microsoft SQL Server 2019 (GA) / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
Microsoft SQL Server 2019 (GA) / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 5.7 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 13 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 5.7 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 5.7 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 13 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 13 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
Microsoft SQL Server 2019 (GA) / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
Microsoft SQL Server 2019 (GA) / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.3 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.3 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.3 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 10.3 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 5.7 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.3 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.3 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.3 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.3 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (GA) / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.3 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.3 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.3 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.3 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2019 (GA) / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.2 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 10 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 10 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 10 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 10.3 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 10 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
Microsoft SQL Server 2017 (Latest) / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
Microsoft SQL Server 2017 (Latest) / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 14 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.7 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.4 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.3 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 14 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.3 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 14 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Microsoft SQL Server 2017 (Latest) / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
PostgreSQL 16 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.3 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.3 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.3 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 10.9 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.3 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 10.5 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.9 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MySQL 8.2 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MySQL 8.2 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 10.5 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.5 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
PostgreSQL 16 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.5 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.5 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 10.5 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.5 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.5 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.5 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.5 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.5 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.5 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.5 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.8 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.0 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.0 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.0 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.0 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 10.6 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.6 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 10.10 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 10.10 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 10.10 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 10.10 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.4 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 10.10 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.2 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.2 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.3 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.3 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.3 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.3 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.2 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.2 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.2 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.3 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.2 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.1 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.2 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.4 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.2 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.2 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.2 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.4 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.3 - L13.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.4 - L11.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.1 / P8.4 - L11.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.1 / P8.4 - L11.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.4 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.3 - L13.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.4 - L10.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.4 - L10.* - prefer-lowest: vendor/laravel/framework/src/Illuminate/Log/Logger.php#L46
Illuminate\Log\Logger::__construct(): Implicitly marking parameter $dispatcher as nullable is deprecated, the explicit nullable type must be used instead
MariaDB 11.1 / P8.1 - L10.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.4 - L12.* - prefer-lowest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
MariaDB 11.1 / P8.4 - L12.* - prefer-stable
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, shivammathur/setup-php@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/