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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

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/yaml 7.3.*, found symfony/yaml[v7.3.0, ..., v7.3.8] but these were not loaded, because they are affected by security advisories ("�]8;;https://symfony.com/cve-2026-45304�\PKSA-v5yj-8nmz-sk2q�]8;;�\", "�]8;;https://symfony.com/cve-2026-45305�\PKSA-ft77-7h5f-p3r6�]8;;�\", "�]8;;https://symfony.com/cve-2026-45133�\PKSA-b14r-zh1d-vdrc�]8;;�\"). Go to https://packagist.org/security-advisories/ to find advisory details. To ignore the advisories, add their IDs to the "policy.advisories.ignore-id" config or add the package to "policy.advisories.ignore". To turn the feature off entirely, you can set "policy.advisories.block" to false.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, technote-space/get-diff-action@v6. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@0400d5f644dc74513175e3cd8d07132dd4860809, technote-space/get-diff-action@v6. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/