Process completed with exit code 2.

Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/string is locked to version v8.0.6 and an update of this package was not requested. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v7.4.7 and an update of this package was not requested. - symfony/console v7.4.7 requires symfony/string ^7.2|^8.0 -> satisfiable by symfony/string[v8.0.6]. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement.

Process completed with exit code 2.

Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/string is locked to version v8.0.6 and an update of this package was not requested. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v7.4.7 and an update of this package was not requested. - symfony/console v7.4.7 requires symfony/string ^7.2|^8.0 -> satisfiable by symfony/string[v8.0.6]. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement.

Process completed with exit code 2.

Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/string is locked to version v8.0.6 and an update of this package was not requested. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v7.4.7 and an update of this package was not requested. - symfony/console v7.4.7 requires symfony/string ^7.2|^8.0 -> satisfiable by symfony/string[v8.0.6]. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement.

Process completed with exit code 2.

Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/string is locked to version v8.0.6 and an update of this package was not requested. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v7.4.7 and an update of this package was not requested. - symfony/console v7.4.7 requires symfony/string ^7.2|^8.0 -> satisfiable by symfony/string[v8.0.6]. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement.

Process completed with exit code 2.

Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/string is locked to version v8.0.6 and an update of this package was not requested. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v7.4.7 and an update of this package was not requested. - symfony/console v7.4.7 requires symfony/string ^7.2|^8.0 -> satisfiable by symfony/string[v8.0.6]. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement.

Process completed with exit code 2.

Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/string is locked to version v8.0.6 and an update of this package was not requested. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v7.4.7 and an update of this package was not requested. - symfony/console v7.4.7 requires symfony/string ^7.2|^8.0 -> satisfiable by symfony/string[v8.0.6]. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement.

Process completed with exit code 2.

Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/string is locked to version v8.0.6 and an update of this package was not requested. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v7.4.7 and an update of this package was not requested. - symfony/console v7.4.7 requires symfony/string ^7.2|^8.0 -> satisfiable by symfony/string[v8.0.6]. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement.

Process completed with exit code 2.

Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/string is locked to version v8.0.6 and an update of this package was not requested. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v7.4.7 and an update of this package was not requested. - symfony/console v7.4.7 requires symfony/string ^7.2|^8.0 -> satisfiable by symfony/string[v8.0.6]. - symfony/string v8.0.6 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement.

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 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@v4. 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@v4. 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@v4. 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@v4. 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@v4. 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@v4. 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@v4. 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@v4. 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@v4. 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@v4. 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@v4. 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@v4. 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/

Calling no_autobump! because: :requires_manual_review is deprecated! There is no replacement.

Calling no_autobump! because: :requires_manual_review is deprecated! There is no replacement.

Calling no_autobump! because: :requires_manual_review is deprecated! There is no replacement.

libtool 2.5.4 is already installed and up-to-date. To reinstall 2.5.4, run: brew reinstall libtool

autoconf 2.72 is already installed and up-to-date. To reinstall 2.72, run: brew reinstall autoconf

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 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/

Calling no_autobump! because: :requires_manual_review is deprecated! There is no replacement.

Calling no_autobump! because: :requires_manual_review is deprecated! There is no replacement.

Calling no_autobump! because: :requires_manual_review is deprecated! There is no replacement.

libtool 2.5.4 is already installed and up-to-date. To reinstall 2.5.4, run: brew reinstall libtool

autoconf 2.72 is already installed and up-to-date. To reinstall 2.72, run: brew reinstall autoconf

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, codecov/test-results-action@v1. 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/

This action is being deprecated in favor of 'codecov-action'. Please update CI accordingly to use 'codecov-action@v5' with 'report_type: test_results'. The 'codecov-action' should and can be run at least once for coverage and once for test results

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, codecov/test-results-action@v1. 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/