Skip to content

Continuous Integration #2299

Continuous Integration

Continuous Integration #2299

Triggered via create March 29, 2026 17:10
Status Failure
Total duration 54s
Artifacts
run  /  Generate test matrix
3s
run / Generate test matrix
Matrix: run / Code Coverage
Matrix: run / Coding Standards
Matrix: run / Lint composer.json
Matrix: run / Mutation Tests
Matrix: run / Static Code Analysis
Matrix: run / tests
Fit to window
Zoom out
Zoom in

Annotations

31 errors and 15 warnings
run / Coding Standards (8.5)
Process completed with exit code 2.
run / Coding Standards (8.5)
Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - maglnet/composer-require-checker is locked to version 4.16.1 and an update of this package was not requested. - maglnet/composer-require-checker 4.16.1 requires php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.5.4) does not satisfy that requirement.
run / Static Code Analysis (8.5)
Process completed with exit code 2.
run / Static Code Analysis (8.5)
Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - maglnet/composer-require-checker is locked to version 4.16.1 and an update of this package was not requested. - maglnet/composer-require-checker 4.16.1 requires php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.5.4) does not satisfy that requirement.
run / Code Coverage (8.5)
Process completed with exit code 2.
run / Code Coverage (8.5)
Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - maglnet/composer-require-checker is locked to version 4.16.1 and an update of this package was not requested. - maglnet/composer-require-checker 4.16.1 requires php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.5.4) does not satisfy that requirement.
run / Test: PHP 8.4, Symfony 7.2, highest)
Process completed with exit code 2.
run / Test: PHP 8.4, Symfony 7.2, highest)
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires symfony/http-foundation ^6.4 || ^7.0, found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 2 - Root composer.json requires symfony/http-kernel ^6.4 || ^7.0 -> satisfiable by symfony/http-kernel[v7.2.0, ..., v7.2.9]. - symfony/http-kernel[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 3 - Root composer.json requires symfony/twig-bundle ^6.4 || ^7.0 -> satisfiable by symfony/twig-bundle[v7.2.0, v7.2.8, v7.2.9]. - symfony/twig-bundle[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 4 - Root composer.json requires nucleos/user-bundle ^3.7 || ^4.0 -> satisfiable by nucleos/user-bundle[3.7.0, 4.0.0]. - nucleos/user-bundle[3.7.0, 4.0.0] require symfony/http-foundation ^6.4 || ^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
run / Test: PHP 8.5, Symfony 6.4, lowest)
Process completed with exit code 2.
run / Test: PHP 8.5, Symfony 6.4, lowest)
Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - maglnet/composer-require-checker is locked to version 4.16.1 and an update of this package was not requested. - maglnet/composer-require-checker 4.16.1 requires php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.5.4) does not satisfy that requirement.
run / Test: PHP 8.5, Symfony 6.4, highest)
Process completed with exit code 2.
run / Test: PHP 8.5, Symfony 6.4, highest)
Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - maglnet/composer-require-checker is locked to version 4.16.1 and an update of this package was not requested. - maglnet/composer-require-checker 4.16.1 requires php ~8.2.0 || ~8.3.0 || ~8.4.0 -> your php version (8.5.4) does not satisfy that requirement.
run / Test: PHP 8.3, Symfony 7.2, highest)
Process completed with exit code 2.
run / Test: PHP 8.3, Symfony 7.2, highest)
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires symfony/http-foundation ^6.4 || ^7.0, found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 2 - Root composer.json requires symfony/http-kernel ^6.4 || ^7.0 -> satisfiable by symfony/http-kernel[v7.2.0, ..., v7.2.9]. - symfony/http-kernel[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 3 - Root composer.json requires symfony/twig-bundle ^6.4 || ^7.0 -> satisfiable by symfony/twig-bundle[v7.2.0, v7.2.8, v7.2.9]. - symfony/twig-bundle[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 4 - Root composer.json requires nucleos/user-bundle ^3.7 || ^4.0 -> satisfiable by nucleos/user-bundle[3.7.0, 4.0.0]. - nucleos/user-bundle[3.7.0, 4.0.0] require symfony/http-foundation ^6.4 || ^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
run / Test: PHP 8.3, Symfony 6.4, highest)
The strategy configuration was canceled because "run.tests._8_4_7_2_highest" failed
run / Test: PHP 8.3, Symfony 6.4, highest)
The operation was canceled.
run / Test: PHP 8.4, Symfony 7.2, lowest)
The strategy configuration was canceled because "run.tests._8_4_7_2_highest" failed
run / Test: PHP 8.4, Symfony 7.2, lowest)
Process completed with exit code 2.
run / Test: PHP 8.4, Symfony 7.2, lowest)
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires symfony/http-foundation ^6.4 || ^7.0, found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 2 - Root composer.json requires symfony/http-kernel ^6.4 || ^7.0 -> satisfiable by symfony/http-kernel[v7.2.0, ..., v7.2.9]. - symfony/http-kernel[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 3 - Root composer.json requires symfony/twig-bundle ^6.4 || ^7.0 -> satisfiable by symfony/twig-bundle[v7.2.0, v7.2.8, v7.2.9]. - symfony/twig-bundle[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 4 - Root composer.json requires nucleos/user-bundle ^3.7 || ^4.0 -> satisfiable by nucleos/user-bundle[3.7.0, 4.0.0]. - nucleos/user-bundle[3.7.0, 4.0.0] require symfony/http-foundation ^6.4 || ^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
run / Test: PHP 8.3, Symfony 7.2, lowest)
The strategy configuration was canceled because "run.tests._8_4_7_2_highest" failed
run / Test: PHP 8.3, Symfony 7.2, lowest)
The operation was canceled.
run / Test: PHP 8.4, Symfony 6.4, highest)
The strategy configuration was canceled because "run.tests._8_4_7_2_highest" failed
run / Test: PHP 8.4, Symfony 6.4, highest)
The operation was canceled.
run / Test: PHP 8.4, Symfony 6.4, lowest)
The strategy configuration was canceled because "run.tests._8_4_7_2_highest" failed
run / Test: PHP 8.4, Symfony 6.4, lowest)
The operation was canceled.
run / Test: PHP 8.3, Symfony 6.4, lowest)
The strategy configuration was canceled because "run.tests._8_4_7_2_highest" failed
run / Test: PHP 8.3, Symfony 6.4, lowest)
The operation was canceled.
run / Test: PHP 8.5, Symfony 7.2, lowest)
Process completed with exit code 2.
run / Test: PHP 8.5, Symfony 7.2, lowest)
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires symfony/http-foundation ^6.4 || ^7.0, found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 2 - Root composer.json requires symfony/http-kernel ^6.4 || ^7.0 -> satisfiable by symfony/http-kernel[v7.2.0, ..., v7.2.9]. - symfony/http-kernel[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 3 - Root composer.json requires symfony/twig-bundle ^6.4 || ^7.0 -> satisfiable by symfony/twig-bundle[v7.2.0, v7.2.8, v7.2.9]. - symfony/twig-bundle[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 4 - Root composer.json requires nucleos/user-bundle ^3.7 || ^4.0 -> satisfiable by nucleos/user-bundle[3.7.0, 4.0.0]. - nucleos/user-bundle[3.7.0, 4.0.0] require symfony/http-foundation ^6.4 || ^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
run / Test: PHP 8.5, Symfony 7.2, highest)
Process completed with exit code 2.
run / Test: PHP 8.5, Symfony 7.2, highest)
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires symfony/http-foundation ^6.4 || ^7.0, found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 2 - Root composer.json requires symfony/http-kernel ^6.4 || ^7.0 -> satisfiable by symfony/http-kernel[v7.2.0, ..., v7.2.9]. - symfony/http-kernel[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 3 - Root composer.json requires symfony/twig-bundle ^6.4 || ^7.0 -> satisfiable by symfony/twig-bundle[v7.2.0, v7.2.8, v7.2.9]. - symfony/twig-bundle[v7.2.0, ..., v7.2.9] require symfony/http-foundation ^6.4|^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config. Problem 4 - Root composer.json requires nucleos/user-bundle ^3.7 || ^4.0 -> satisfiable by nucleos/user-bundle[3.7.0, 4.0.0]. - nucleos/user-bundle[3.7.0, 4.0.0] require symfony/http-foundation ^6.4 || ^7.0 -> found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.0.0, ..., v7.4.7] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/blog/cve-2025-64500-incorrect-parsing-of-path-info-can-lead-to-limited-authorization-bypass�\PKSA-365x-2zjk-pt47�]8;;�\", "�]8;;https://symfony.com/cve-2024-50345�\PKSA-b35n-565h-rs4q�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add them to the audit "ignore" config. To turn the feature off entirely, you can set "block-insecure" to false in your "audit" config.
run / Coding Standards (8.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Mutation Tests (8.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Static Code Analysis (8.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Code Coverage (8.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Test: PHP 8.4, Symfony 7.2, highest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Lint composer.json (8.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Test: PHP 8.5, Symfony 6.4, lowest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Test: PHP 8.5, Symfony 6.4, highest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Test: PHP 8.3, Symfony 7.2, highest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Test: PHP 8.4, Symfony 7.2, lowest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Test: PHP 8.4, Symfony 6.4, highest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Test: PHP 8.4, Symfony 6.4, lowest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Test: PHP 8.3, Symfony 6.4, lowest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Test: PHP 8.5, Symfony 7.2, lowest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
run / Test: PHP 8.5, Symfony 7.2, highest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/