Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires symfony/http-foundation ^6.4 || ^7.2, found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.2.0, ..., v7.4.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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.1 || ^7.2 -> 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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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/security-bundle ^6.4 || ^7.2 -> satisfiable by symfony/security-bundle[v7.2.0, ..., v7.2.9]. - symfony/security-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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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 symfony/security-http ^6.4 || ^7.2 -> satisfiable by symfony/security-http[v7.2.0, ..., v7.2.9]. - symfony/security-http[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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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 5 - Root composer.json requires symfony/twig-bundle ^6.4 || ^7.2 -> 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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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 6 - Root composer.json requires symfony/web-profiler-bundle ^6.4 || ^7.2 -> satisfiable by symfony/web-profiler-bundle[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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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. - symfony/web-profiler-bundle[v7.2.0, ..., v7.2.9] require symfony/http-kernel ^6.4|^7.0 -> satisfiable by symfony/http-kernel[v7.2.0, ...,

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires symfony/http-foundation ^6.4 || ^7.2, found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.2.0, ..., v7.4.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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.1 || ^7.2 -> 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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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/security-bundle ^6.4 || ^7.2 -> satisfiable by symfony/security-bundle[v7.2.0, ..., v7.2.9]. - symfony/security-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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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 symfony/security-http ^6.4 || ^7.2 -> satisfiable by symfony/security-http[v7.2.0, ..., v7.2.9]. - symfony/security-http[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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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 5 - Root composer.json requires symfony/twig-bundle ^6.4 || ^7.2 -> 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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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 6 - Root composer.json requires symfony/web-profiler-bundle ^6.4 || ^7.2 -> satisfiable by symfony/web-profiler-bundle[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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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. - symfony/web-profiler-bundle[v7.2.0, ..., v7.2.9] require symfony/http-kernel ^6.4|^7.0 -> satisfiable by symfony/http-kernel[v7.2.0, ...,

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires symfony/http-foundation ^6.4 || ^7.2, found symfony/http-foundation[v6.4.0, ..., v6.4.35, v7.2.0, ..., v7.4.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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.1 || ^7.2 -> 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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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/security-bundle ^6.4 || ^7.2 -> satisfiable by symfony/security-bundle[v7.2.0, ..., v7.2.9]. - symfony/security-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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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 symfony/security-http ^6.4 || ^7.2 -> satisfiable by symfony/security-http[v7.2.0, ..., v7.2.9]. - symfony/security-http[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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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 5 - Root composer.json requires symfony/twig-bundle ^6.4 || ^7.2 -> 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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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 6 - Root composer.json requires symfony/web-profiler-bundle ^6.4 || ^7.2 -> satisfiable by symfony/web-profiler-bundle[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.8] but these were not loaded, because they are affected by security advisories ("PKSA-365x-2zjk-pt47", "PKSA-b35n-565h-rs4q"). 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. - symfony/web-profiler-bundle[v7.2.0, ..., v7.2.9] require symfony/http-kernel ^6.4|^7.0 -> satisfiable by symfony/http-kernel[v7.2.0, ...,

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, notiz-dev/github-action-json-property@release. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/