Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.1.33) does not satisfy that requirement. Problem 2 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.1.33) does not satisfy that requirement. Problem 3 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.1.33) does not satisfy that requirement. Problem 4 - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.1.33) does not satisfy that requirement. - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8].

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.2.34) does not satisfy that requirement. Problem 2 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.2.34) does not satisfy that requirement. Problem 3 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.2.34) does not satisfy that requirement. Problem 4 - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8]. - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.2.34) does not satisfy that requirement.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.4.33) does not satisfy that requirement. Problem 2 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.4.33) does not satisfy that requirement. Problem 3 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.4.33) does not satisfy that requirement. Problem 4 - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8]. - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.4.33) does not satisfy that requirement.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.3.33) does not satisfy that requirement. Problem 2 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.3.33) does not satisfy that requirement. Problem 3 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.3.33) does not satisfy that requirement. Problem 4 - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8]. - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.3.33) does not satisfy that requirement.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.1.33) does not satisfy that requirement. Problem 2 - Root composer.json requires PHP extension ext-pcov * but it is missing from your system. Install or enable PHP's pcov extension. Problem 3 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.1.33) does not satisfy that requirement. Problem 4 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.1.33) does not satisfy that requirement. Problem 5 - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.1.33) does not satisfy that requirement. - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8]. To enable extensions, verify that they are enabled in your .ini files: - C:\tools\php\php.ini You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode. Alternatively, you can run Composer with `--ignore-platform-req=ext-pcov` to temporarily ignore these required extensions.

Process completed with exit code 1.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.4.33) does not satisfy that requirement. Problem 2 - Root composer.json requires PHP extension ext-pcov * but it is missing from your system. Install or enable PHP's pcov extension. Problem 3 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.4.33) does not satisfy that requirement. Problem 4 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.4.33) does not satisfy that requirement. Problem 5 - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8]. - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.4.33) does not satisfy that requirement. To enable extensions, verify that they are enabled in your .ini files: - C:\tools\php\php.ini You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode. Alternatively, you can run Composer with `--ignore-platform-req=ext-pcov` to temporarily ignore these required extensions.

Process completed with exit code 1.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.3.33) does not satisfy that requirement. Problem 2 - Root composer.json requires PHP extension ext-pcov * but it is missing from your system. Install or enable PHP's pcov extension. Problem 3 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.3.33) does not satisfy that requirement. Problem 4 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.3.33) does not satisfy that requirement. Problem 5 - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8]. - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.3.33) does not satisfy that requirement. To enable extensions, verify that they are enabled in your .ini files: - C:\tools\php\php.ini You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode. Alternatively, you can run Composer with `--ignore-platform-req=ext-pcov` to temporarily ignore these required extensions.

Process completed with exit code 1.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.2.34) does not satisfy that requirement. Problem 2 - Root composer.json requires PHP extension ext-pcov * but it is missing from your system. Install or enable PHP's pcov extension. Problem 3 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.2.34) does not satisfy that requirement. Problem 4 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.2.34) does not satisfy that requirement. Problem 5 - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8]. - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.2.34) does not satisfy that requirement. To enable extensions, verify that they are enabled in your .ini files: - C:\tools\php\php.ini You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode. Alternatively, you can run Composer with `--ignore-platform-req=ext-pcov` to temporarily ignore these required extensions.

Process completed with exit code 1.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.3.33) does not satisfy that requirement. Problem 2 - Root composer.json requires PHP extension ext-pcov * but it is missing from your system. Install or enable PHP's pcov extension. Problem 3 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.3.33) does not satisfy that requirement. Problem 4 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.3.33) does not satisfy that requirement. Problem 5 - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8]. - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.3.33) does not satisfy that requirement. To enable extensions, verify that they are enabled in your .ini files: - /opt/homebrew/etc/php/7.3/php.ini - /opt/homebrew/etc/php/7.3/conf.d/20-xdebug.ini - /opt/homebrew/etc/php/7.3/conf.d/ext-opcache.ini You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode. Alternatively, you can run Composer with `--ignore-platform-req=ext-pcov` to temporarily ignore these required extensions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.1.33) does not satisfy that requirement. Problem 2 - Root composer.json requires PHP extension ext-pcov * but it is missing from your system. Install or enable PHP's pcov extension. Problem 3 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.1.33) does not satisfy that requirement. Problem 4 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.1.33) does not satisfy that requirement. Problem 5 - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.1.33) does not satisfy that requirement. - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8]. To enable extensions, verify that they are enabled in your .ini files: - /opt/homebrew/etc/php/7.1/php.ini - /opt/homebrew/etc/php/7.1/conf.d/20-xdebug.ini - /opt/homebrew/etc/php/7.1/conf.d/ext-opcache.ini You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode. Alternatively, you can run Composer with `--ignore-platform-req=ext-pcov` to temporarily ignore these required extensions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.4.33) does not satisfy that requirement. Problem 2 - Root composer.json requires PHP extension ext-pcov * but it is missing from your system. Install or enable PHP's pcov extension. Problem 3 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.4.33) does not satisfy that requirement. Problem 4 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.4.33) does not satisfy that requirement. Problem 5 - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8]. - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.4.33) does not satisfy that requirement. To enable extensions, verify that they are enabled in your .ini files: - /opt/homebrew/etc/php/7.4/php.ini - /opt/homebrew/etc/php/7.4/conf.d/20-xdebug.ini - /opt/homebrew/etc/php/7.4/conf.d/ext-opcache.ini You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode. Alternatively, you can run Composer with `--ignore-platform-req=ext-pcov` to temporarily ignore these required extensions.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php >= 8.2 but your php version (7.2.34) does not satisfy that requirement. Problem 2 - Root composer.json requires PHP extension ext-pcov * but it is missing from your system. Install or enable PHP's pcov extension. Problem 3 - Root composer.json requires symfony/finder ^7.2 -> satisfiable by symfony/finder[v7.2.0, v7.2.2]. - symfony/finder[v7.2.0, ..., v7.2.2] require php >=8.2 -> your php version (7.2.34) does not satisfy that requirement. Problem 4 - Root composer.json requires symfony/yaml ^7.2 -> satisfiable by symfony/yaml[v7.2.0]. - symfony/yaml v7.2.0 requires php >=8.2 -> your php version (7.2.34) does not satisfy that requirement. Problem 5 - Root composer.json requires phpunit/php-code-coverage ^11 -> satisfiable by phpunit/php-code-coverage[11.0.0, ..., 11.0.8]. - phpunit/php-code-coverage[11.0.5, ..., 11.0.8] require php >=8.2 -> your php version (7.2.34) does not satisfy that requirement. To enable extensions, verify that they are enabled in your .ini files: - /opt/homebrew/etc/php/7.2/php.ini - /opt/homebrew/etc/php/7.2/conf.d/20-xdebug.ini - /opt/homebrew/etc/php/7.2/conf.d/ext-opcache.ini You can also run `php --ini` in a terminal to see which files are used by PHP in CLI mode. Alternatively, you can run Composer with `--ignore-platform-req=ext-pcov` to temporarily ignore these required extensions.

Process completed with exit code 2.

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v1. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/