Skip to content

Magento 2 Recipe Setup Upgrade Task Should be Non Interactive #4178 (… #2288

Magento 2 Recipe Setup Upgrade Task Should be Non Interactive #4178 (…

Magento 2 Recipe Setup Upgrade Task Should be Non Interactive #4178 (… #2288

Triggered via push April 1, 2026 16:12
Status Failure
Total duration 16s
Artifacts

test.yml

on: push
Matrix: unit
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
unit (8.2)
Process completed with exit code 2.
unit (8.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.8 and an update of this package was not requested. - symfony/string v8.0.8 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement. Problem 2 - symfony/event-dispatcher is locked to version v8.0.8 and an update of this package was not requested. - symfony/event-dispatcher v8.0.8 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement. Problem 3 - symfony/filesystem is locked to version v8.0.8 and an update of this package was not requested. - symfony/filesystem v8.0.8 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement. Problem 4 - symfony/finder is locked to version v8.0.8 and an update of this package was not requested. - symfony/finder v8.0.8 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement. Problem 5 - symfony/options-resolver is locked to version v8.0.8 and an update of this package was not requested. - symfony/options-resolver v8.0.8 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement. Problem 6 - symfony/stopwatch is locked to version v8.0.8 and an update of this package was not requested. - symfony/stopwatch v8.0.8 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement. Problem 7 - symfony/console is locked to version v7.4.8 and an update of this package was not requested. - symfony/console v7.4.8 requires symfony/string ^7.2|^8.0 -> satisfiable by symfony/string[v8.0.8]. - symfony/string v8.0.8 requires php >=8.4 -> your php version (8.2.30) does not satisfy that requirement.
unit (8.3)
The strategy configuration was canceled because "unit._8_2" failed
unit (8.3)
Process completed with exit code 2.
unit (8.3)
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.8 and an update of this package was not requested. - symfony/string v8.0.8 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 2 - symfony/event-dispatcher is locked to version v8.0.8 and an update of this package was not requested. - symfony/event-dispatcher v8.0.8 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 3 - symfony/filesystem is locked to version v8.0.8 and an update of this package was not requested. - symfony/filesystem v8.0.8 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 4 - symfony/finder is locked to version v8.0.8 and an update of this package was not requested. - symfony/finder v8.0.8 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 5 - symfony/options-resolver is locked to version v8.0.8 and an update of this package was not requested. - symfony/options-resolver v8.0.8 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 6 - symfony/stopwatch is locked to version v8.0.8 and an update of this package was not requested. - symfony/stopwatch v8.0.8 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 7 - symfony/console is locked to version v7.4.8 and an update of this package was not requested. - symfony/console v7.4.8 requires symfony/string ^7.2|^8.0 -> satisfiable by symfony/string[v8.0.8]. - symfony/string v8.0.8 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement.
unit (8.2)
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/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
unit (8.3)
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/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/