Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - drupal/core-recommended is locked to version 10.6.10 and an update of this package was not requested. - drupal/core-recommended 10.6.10 requires guzzlehttp/psr7 ~2.8.0 -> found guzzlehttp/psr7[2.8.0, 2.8.1] but these were not loaded, because they are affected by security advisories ("PKSA-jj5t-2zs1-dcfm", "PKSA-gm5x-j3mz-71n9"). 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. Problem 2 - Root composer.json requires drupal/jsonapi_frontend ^1 -> satisfiable by drupal/jsonapi_frontend[1.0.2, ..., 1.0.10]. - drupal/core 10.6.10 requires guzzlehttp/psr7 ^2.4.5 -> found guzzlehttp/psr7[2.4.5, ..., 2.11.0] but these were not loaded, because they are affected by security advisories ("PKSA-jj5t-2zs1-dcfm", "PKSA-gm5x-j3mz-71n9"). 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. - drupal/jsonapi_frontend[1.0.2, ..., 1.0.10] require drupal/core ^10 || ^11 -> satisfiable by drupal/core[10.5.10, 10.5.11, 10.6.9, 10.6.10, 11.2.12, 11.2.13, 11.3.10, 11.3.11].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - drupal/core-recommended is locked to version 11.3.11 and an update of this package was not requested. - drupal/core-recommended 11.3.11 requires guzzlehttp/psr7 ~2.8.0 -> found guzzlehttp/psr7[2.8.0, 2.8.1] but these were not loaded, because they are affected by security advisories ("PKSA-jj5t-2zs1-dcfm", "PKSA-gm5x-j3mz-71n9"). 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. Problem 2 - Root composer.json requires drupal/jsonapi_frontend ^1 -> satisfiable by drupal/jsonapi_frontend[1.0.2, ..., 1.0.10]. - drupal/core 11.3.11 requires guzzlehttp/psr7 ^2.8.0 -> found guzzlehttp/psr7[2.8.0, ..., 2.11.0] but these were not loaded, because they are affected by security advisories ("PKSA-jj5t-2zs1-dcfm", "PKSA-gm5x-j3mz-71n9"). 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. - drupal/jsonapi_frontend[1.0.2, ..., 1.0.10] require drupal/core ^10 || ^11 -> satisfiable by drupal/core[10.5.10, 10.5.11, 10.6.9, 10.6.10, 11.2.12, 11.2.13, 11.3.10, 11.3.11].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - drupal/core-recommended is locked to version 11.3.11 and an update of this package was not requested. - drupal/core-recommended 11.3.11 requires guzzlehttp/psr7 ~2.8.0 -> found guzzlehttp/psr7[2.8.0, 2.8.1] but these were not loaded, because they are affected by security advisories ("PKSA-jj5t-2zs1-dcfm", "PKSA-gm5x-j3mz-71n9"). 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. Problem 2 - Root composer.json requires drupal/jsonapi_frontend ^1 -> satisfiable by drupal/jsonapi_frontend[1.0.2, ..., 1.0.10]. - drupal/core 11.3.11 requires guzzlehttp/psr7 ^2.8.0 -> found guzzlehttp/psr7[2.8.0, ..., 2.11.0] but these were not loaded, because they are affected by security advisories ("PKSA-jj5t-2zs1-dcfm", "PKSA-gm5x-j3mz-71n9"). 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. - drupal/jsonapi_frontend[1.0.2, ..., 1.0.10] require drupal/core ^10 || ^11 -> satisfiable by drupal/core[10.5.10, 10.5.11, 10.6.9, 10.6.10, 11.2.12, 11.2.13, 11.3.10, 11.3.11].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - drupal/core-recommended is locked to version 11.3.11 and an update of this package was not requested. - drupal/core-recommended 11.3.11 requires guzzlehttp/psr7 ~2.8.0 -> found guzzlehttp/psr7[2.8.0, 2.8.1] but these were not loaded, because they are affected by security advisories ("PKSA-jj5t-2zs1-dcfm", "PKSA-gm5x-j3mz-71n9"). 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. Problem 2 - Root composer.json requires drupal/jsonapi_frontend ^1 -> satisfiable by drupal/jsonapi_frontend[1.0.2, ..., 1.0.10]. - drupal/core 11.3.11 requires guzzlehttp/psr7 ^2.8.0 -> found guzzlehttp/psr7[2.8.0, ..., 2.11.0] but these were not loaded, because they are affected by security advisories ("PKSA-jj5t-2zs1-dcfm", "PKSA-gm5x-j3mz-71n9"). 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. - drupal/jsonapi_frontend[1.0.2, ..., 1.0.10] require drupal/core ^10 || ^11 -> satisfiable by drupal/core[10.5.10, 10.5.11, 10.6.9, 10.6.10, 11.2.12, 11.2.13, 11.3.10, 11.3.11].

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/