Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires squizlabs/php_codesniffer dev-3.x, found squizlabs/php_codesniffer[dev-TEST/ghactions-revert-code-coverage-php-version, dev-feature/ghactions-test-against-libxml-2.14, dev-dependabot/github_actions/3.x/ramsey/composer-install-4.0.0, dev-dependabot/github_actions/3.x/octokit/request-action-3.0.0, dev-dependabot/github_actions/3.x/action-runners-bb9b65ea23, dev-dependabot/github_actions/3.x/action-runners-493d9363a6, dev-feature/3.x-metrics-for-switch-statements, dev-feature/3769-improve-todo-fixme-sniffs, dev-feature/psr2-namespacedeclaration-bow-out-on-php-close-tag, 1.4.2, ..., 1.5.x-dev, 2.0.0a1, ..., 2.9.x-dev, 3.0.0a1, ..., 3.x-dev, 4.0.0beta1, ..., 4.x-dev] but it does not match the constraint. Problem 2 - Root composer.json requires phpcsstandards/phpcsextra dev-develop -> satisfiable by phpcsstandards/phpcsextra[dev-develop]. - phpcsstandards/phpcsextra dev-develop requires squizlabs/php_codesniffer ^3.13.5 || ^4.0.1 -> found squizlabs/php_codesniffer[3.13.5, 3.x-dev, 4.0.1, 4.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 3 - Root composer.json requires phpcsstandards/phpcsutils dev-develop -> satisfiable by phpcsstandards/phpcsutils[dev-develop]. - phpcsstandards/phpcsutils dev-develop requires squizlabs/php_codesniffer ^3.13.5 || ^4.0.1 -> found squizlabs/php_codesniffer[3.13.5, 3.x-dev, 4.0.1, 4.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 4 - Root composer.json requires wp-coding-standards/wpcs dev-develop -> satisfiable by wp-coding-standards/wpcs[dev-develop]. - wp-coding-standards/wpcs dev-develop requires squizlabs/php_codesniffer ^3.13.4 -> found squizlabs/php_codesniffer[3.13.4, 3.13.5, 3.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 5 - Root composer.json requires phpcompatibility/php-compatibility ^9 -> satisfiable by phpcompatibility/php-compatibility[9.0.0, ..., 9.3.5]. - phpcompatibility/php-compatibility[9.0.0, ..., 9.3.5] require squizlabs/php_codesniffer ^2.3 || ^3.0.2 -> found squizlabs/php_codesniffer[2.3.0, ..., 2.9.x-dev, 3.0.2, ..., 3.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 6 - Root composer.json requires phpcsstandards/phpcsdevtools ^1.2.3 -> satisfiable by phpcsstandards/phpcsdevtools[1.2.3]. - phpcsstandards/phpcsdevtools 1.2.3 requires squizlabs/php_codesniffer ^3.1.0 || ^4.0 -> found squizlabs/php_codesniffer[3.1.0, ..., 3.x-dev, 4.0.0beta1, ..., 4.x-dev] but it conflicts with your root composer.json require (dev-3.x).

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires squizlabs/php_codesniffer dev-3.x, found squizlabs/php_codesniffer[dev-TEST/ghactions-revert-code-coverage-php-version, dev-feature/ghactions-test-against-libxml-2.14, dev-dependabot/github_actions/3.x/ramsey/composer-install-4.0.0, dev-dependabot/github_actions/3.x/octokit/request-action-3.0.0, dev-dependabot/github_actions/3.x/action-runners-bb9b65ea23, dev-dependabot/github_actions/3.x/action-runners-493d9363a6, dev-feature/3.x-metrics-for-switch-statements, dev-feature/3769-improve-todo-fixme-sniffs, dev-feature/psr2-namespacedeclaration-bow-out-on-php-close-tag, 1.4.2, ..., 1.5.x-dev, 2.0.0a1, ..., 2.9.x-dev, 3.0.0a1, ..., 3.x-dev, 4.0.0beta1, ..., 4.x-dev] but it does not match the constraint. Problem 2 - Root composer.json requires phpcsstandards/phpcsextra dev-develop -> satisfiable by phpcsstandards/phpcsextra[dev-develop]. - phpcsstandards/phpcsextra dev-develop requires squizlabs/php_codesniffer ^3.13.5 || ^4.0.1 -> found squizlabs/php_codesniffer[3.13.5, 3.x-dev, 4.0.1, 4.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 3 - Root composer.json requires phpcsstandards/phpcsutils dev-develop -> satisfiable by phpcsstandards/phpcsutils[dev-develop]. - phpcsstandards/phpcsutils dev-develop requires squizlabs/php_codesniffer ^3.13.5 || ^4.0.1 -> found squizlabs/php_codesniffer[3.13.5, 3.x-dev, 4.0.1, 4.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 4 - Root composer.json requires wp-coding-standards/wpcs dev-develop -> satisfiable by wp-coding-standards/wpcs[dev-develop]. - wp-coding-standards/wpcs dev-develop requires squizlabs/php_codesniffer ^3.13.4 -> found squizlabs/php_codesniffer[3.13.4, 3.13.5, 3.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 5 - Root composer.json requires phpcompatibility/php-compatibility ^9 -> satisfiable by phpcompatibility/php-compatibility[9.0.0, ..., 9.3.5]. - phpcompatibility/php-compatibility[9.0.0, ..., 9.3.5] require squizlabs/php_codesniffer ^2.3 || ^3.0.2 -> found squizlabs/php_codesniffer[2.3.0, ..., 2.9.x-dev, 3.0.2, ..., 3.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 6 - Root composer.json requires phpcsstandards/phpcsdevtools ^1.2.3 -> satisfiable by phpcsstandards/phpcsdevtools[1.2.3]. - phpcsstandards/phpcsdevtools 1.2.3 requires squizlabs/php_codesniffer ^3.1.0 || ^4.0 -> found squizlabs/php_codesniffer[3.1.0, ..., 3.x-dev, 4.0.0beta1, ..., 4.x-dev] but it conflicts with your root composer.json require (dev-3.x).

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires squizlabs/php_codesniffer dev-3.x, found squizlabs/php_codesniffer[dev-TEST/ghactions-revert-code-coverage-php-version, dev-feature/ghactions-test-against-libxml-2.14, dev-dependabot/github_actions/3.x/ramsey/composer-install-4.0.0, dev-dependabot/github_actions/3.x/octokit/request-action-3.0.0, dev-dependabot/github_actions/3.x/action-runners-bb9b65ea23, dev-dependabot/github_actions/3.x/action-runners-493d9363a6, dev-feature/3.x-metrics-for-switch-statements, dev-feature/3769-improve-todo-fixme-sniffs, dev-feature/psr2-namespacedeclaration-bow-out-on-php-close-tag, 1.4.2, ..., 1.5.x-dev, 2.0.0a1, ..., 2.9.x-dev, 3.0.0a1, ..., 3.x-dev, 4.0.0beta1, ..., 4.x-dev] but it does not match the constraint. Problem 2 - Root composer.json requires phpcsstandards/phpcsextra dev-develop -> satisfiable by phpcsstandards/phpcsextra[dev-develop]. - phpcsstandards/phpcsextra dev-develop requires squizlabs/php_codesniffer ^3.13.5 || ^4.0.1 -> found squizlabs/php_codesniffer[3.13.5, 3.x-dev, 4.0.1, 4.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 3 - Root composer.json requires phpcsstandards/phpcsutils dev-develop -> satisfiable by phpcsstandards/phpcsutils[dev-develop]. - phpcsstandards/phpcsutils dev-develop requires squizlabs/php_codesniffer ^3.13.5 || ^4.0.1 -> found squizlabs/php_codesniffer[3.13.5, 3.x-dev, 4.0.1, 4.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 4 - Root composer.json requires wp-coding-standards/wpcs dev-develop -> satisfiable by wp-coding-standards/wpcs[dev-develop]. - wp-coding-standards/wpcs dev-develop requires squizlabs/php_codesniffer ^3.13.4 -> found squizlabs/php_codesniffer[3.13.4, 3.13.5, 3.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 5 - Root composer.json requires phpcompatibility/php-compatibility ^9 -> satisfiable by phpcompatibility/php-compatibility[9.0.0, ..., 9.3.5]. - phpcompatibility/php-compatibility[9.0.0, ..., 9.3.5] require squizlabs/php_codesniffer ^2.3 || ^3.0.2 -> found squizlabs/php_codesniffer[2.3.0, ..., 2.9.x-dev, 3.0.2, ..., 3.x-dev] but it conflicts with your root composer.json require (dev-3.x). Problem 6 - Root composer.json requires phpcsstandards/phpcsdevtools ^1.2.3 -> satisfiable by phpcsstandards/phpcsdevtools[1.2.3]. - phpcsstandards/phpcsdevtools 1.2.3 requires squizlabs/php_codesniffer ^3.1.0 || ^4.0 -> found squizlabs/php_codesniffer[3.1.0, ..., 3.x-dev, 4.0.0beta1, ..., 4.x-dev] but it conflicts with your root composer.json require (dev-3.x).

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

The strategy configuration was canceled because "test._8_4_dev" failed

The operation was canceled.

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