Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/finder v6.1.3 requires php >=8.1 -> your php version (7.3.33) does not satisfy that requirement. - wp-cli/core-command v2.1.4 requires wp-cli/wp-cli ^2.5.1 -> satisfiable by wp-cli/wp-cli[v2.6.0]. - wp-cli/wp-cli v2.6.0 requires symfony/finder >2.7 -> satisfiable by symfony/finder[v6.1.3]. - wp-cli/core-command is locked to version v2.1.4 and an update of this package was not requested.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/finder v6.1.3 requires php >=8.1 -> your php version (7.3.33) does not satisfy that requirement. - wp-cli/core-command v2.1.4 requires wp-cli/wp-cli ^2.5.1 -> satisfiable by wp-cli/wp-cli[v2.6.0]. - wp-cli/wp-cli v2.6.0 requires symfony/finder >2.7 -> satisfiable by symfony/finder[v6.1.3]. - wp-cli/core-command is locked to version v2.1.4 and an update of this package was not requested.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/finder v6.1.3 requires php >=8.1 -> your php version (7.3.33) does not satisfy that requirement. - wp-cli/core-command v2.1.4 requires wp-cli/wp-cli ^2.5.1 -> satisfiable by wp-cli/wp-cli[v2.6.0]. - wp-cli/wp-cli v2.6.0 requires symfony/finder >2.7 -> satisfiable by symfony/finder[v6.1.3]. - wp-cli/core-command is locked to version v2.1.4 and an update of this package was not requested.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/finder v6.1.3 requires php >=8.1 -> your php version (7.3.33) does not satisfy that requirement. - wp-cli/core-command v2.1.4 requires wp-cli/wp-cli ^2.5.1 -> satisfiable by wp-cli/wp-cli[v2.6.0]. - wp-cli/wp-cli v2.6.0 requires symfony/finder >2.7 -> satisfiable by symfony/finder[v6.1.3]. - wp-cli/core-command is locked to version v2.1.4 and an update of this package was not requested.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/finder v6.1.3 requires php >=8.1 -> your php version (7.3.33) does not satisfy that requirement. - wp-cli/core-command v2.1.4 requires wp-cli/wp-cli ^2.5.1 -> satisfiable by wp-cli/wp-cli[v2.6.0]. - wp-cli/wp-cli v2.6.0 requires symfony/finder >2.7 -> satisfiable by symfony/finder[v6.1.3]. - wp-cli/core-command is locked to version v2.1.4 and an update of this package was not requested.

Process completed with exit code 2.

Your requirements could not be resolved to an installable set of packages. Problem 1 - symfony/finder v6.1.3 requires php >=8.1 -> your php version (7.3.33) does not satisfy that requirement. - wp-cli/core-command v2.1.4 requires wp-cli/wp-cli ^2.5.1 -> satisfiable by wp-cli/wp-cli[v2.6.0]. - wp-cli/wp-cli v2.6.0 requires symfony/finder >2.7 -> satisfiable by symfony/finder[v6.1.3]. - wp-cli/core-command is locked to version v2.1.4 and an update of this package was not requested.

The operation was canceled.

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

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 following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/