Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/config is locked to version v7.0.0 and an update of this package was not requested. - symfony/config v7.0.0 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v7.0.1 and an update of this package was not requested. - symfony/console v7.0.1 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 3 - symfony/dependency-injection is locked to version v7.0.1 and an update of this package was not requested. - symfony/dependency-injection v7.0.1 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 4 - symfony/deprecation-contracts is locked to version v3.4.0 and an update of this package was not requested. - symfony/deprecation-contracts v3.4.0 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement. Problem 5 - symfony/filesystem is locked to version v7.0.0 and an update of this package was not requested. - symfony/filesystem v7.0.0 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 6 - symfony/process is locked to version v7.0.0 and an update of this package was not requested. - symfony/process v7.0.0 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 7 - symfony/service-contracts is locked to version v3.4.0 and an update of this package was not requested. - symfony/service-contracts v3.4.0 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement. Problem 8 - symfony/string is locked to version v7.0.0 and an update of this package was not requested. - symfony/string v7.0.0 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 9 - symfony/var-exporter is locked to version v7.0.1 and an update of this package was not requested. - symfony/var-exporter v7.0.1 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 10 - symfony/yaml is locked to version v7.0.0 and an update of this package was not requested. - symfony/yaml v7.0.0 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 11 - doctrine/instantiator is locked to version 2.0.0 and an update of this package was not requested. - doctrine/instantiator 2.0.0 requires php ^8.1 -> your php version (8.0.30) does not satisfy that requirement. Problem 12 - symfony/event-dispatcher is locked to version v7.0.0 and an update of this package was not requested. - symfony/event-dispatcher v7.0.0 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 13 - symfony/event-dispatcher-contracts is locked to version v3.4.0 and an update of this package was not requested. - symfony/event-dispatcher-contracts v3.4.0 requires php >=8.1 -> your php version (8.0.30) does not satisfy that requirement. Problem 14 - symfony/finder is locked to version v7.0.0 and an update of this package was not requested. - symfony/finder v7.0.0 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 15 - symfony/options-resolver is locked to version v7.0.0 and an update of this package was not requested. - symfony/options-resolver v7.0.0 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 16 - symfony/stopwatch is locked to version v7.0.0 and an update of this package was not requested. - symfony/stopwatch v7.0.0 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. Problem 17 - symfony/filesystem v7.0.0 requires php >=8.2 -> your php version (8.0.30) does not satisfy that requirement. - vimeo/psalm 5.17.0 requires symfony/filesystem ^5.4 || ^6.0 || ^7.0 -> satisfiable by symfony/filesystem[v7.0.0]. - vimeo/psalm

Process completed with exit code 2.

Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/config is locked to version v7.0.0 and an update of this package was not requested. - symfony/config v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v7.0.1 and an update of this package was not requested. - symfony/console v7.0.1 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 3 - symfony/dependency-injection is locked to version v7.0.1 and an update of this package was not requested. - symfony/dependency-injection v7.0.1 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 4 - symfony/filesystem is locked to version v7.0.0 and an update of this package was not requested. - symfony/filesystem v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 5 - symfony/process is locked to version v7.0.0 and an update of this package was not requested. - symfony/process v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 6 - symfony/string is locked to version v7.0.0 and an update of this package was not requested. - symfony/string v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 7 - symfony/var-exporter is locked to version v7.0.1 and an update of this package was not requested. - symfony/var-exporter v7.0.1 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 8 - symfony/yaml is locked to version v7.0.0 and an update of this package was not requested. - symfony/yaml v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 9 - symfony/event-dispatcher is locked to version v7.0.0 and an update of this package was not requested. - symfony/event-dispatcher v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 10 - symfony/finder is locked to version v7.0.0 and an update of this package was not requested. - symfony/finder v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 11 - symfony/options-resolver is locked to version v7.0.0 and an update of this package was not requested. - symfony/options-resolver v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 12 - symfony/stopwatch is locked to version v7.0.0 and an update of this package was not requested. - symfony/stopwatch v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 13 - symfony/filesystem v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. - vimeo/psalm 5.17.0 requires symfony/filesystem ^5.4 || ^6.0 || ^7.0 -> satisfiable by symfony/filesystem[v7.0.0]. - vimeo/psalm is locked to version 5.17.0 and an update of this package was not requested.

Process completed with exit code 2.

Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/config is locked to version v7.0.0 and an update of this package was not requested. - symfony/config v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 2 - symfony/console is locked to version v7.0.1 and an update of this package was not requested. - symfony/console v7.0.1 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 3 - symfony/dependency-injection is locked to version v7.0.1 and an update of this package was not requested. - symfony/dependency-injection v7.0.1 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 4 - symfony/filesystem is locked to version v7.0.0 and an update of this package was not requested. - symfony/filesystem v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 5 - symfony/process is locked to version v7.0.0 and an update of this package was not requested. - symfony/process v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 6 - symfony/string is locked to version v7.0.0 and an update of this package was not requested. - symfony/string v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 7 - symfony/var-exporter is locked to version v7.0.1 and an update of this package was not requested. - symfony/var-exporter v7.0.1 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 8 - symfony/yaml is locked to version v7.0.0 and an update of this package was not requested. - symfony/yaml v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 9 - symfony/event-dispatcher is locked to version v7.0.0 and an update of this package was not requested. - symfony/event-dispatcher v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 10 - symfony/finder is locked to version v7.0.0 and an update of this package was not requested. - symfony/finder v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 11 - symfony/options-resolver is locked to version v7.0.0 and an update of this package was not requested. - symfony/options-resolver v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 12 - symfony/stopwatch is locked to version v7.0.0 and an update of this package was not requested. - symfony/stopwatch v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. Problem 13 - symfony/filesystem v7.0.0 requires php >=8.2 -> your php version (8.1.26) does not satisfy that requirement. - vimeo/psalm 5.17.0 requires symfony/filesystem ^5.4 || ^6.0 || ^7.0 -> satisfiable by symfony/filesystem[v7.0.0]. - vimeo/psalm is locked to version 5.17.0 and an update of this package was not requested.

Process completed with exit code 2.

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