Skip to content
test

Update PHP version and dependencies in workflow and composer files #2

Sign in to view logs

Update PHP version and dependencies in workflow and composer files

Update PHP version and dependencies in workflow and composer files #2

Triggered via push April 1, 2026 19:10
@antonmedvantonmedv
pushed c4d1364
master
Status Failure
Total duration 23s
Artifacts –

test.yaml

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

Annotations

6 errors and 3 warnings
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/console is locked to version v8.0.8 and an update of this package was not requested. - symfony/console v8.0.8 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 2 - symfony/process is locked to version v8.0.8 and an update of this package was not requested. - symfony/process v8.0.8 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 3 - 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 4 - symfony/yaml is locked to version v8.0.8 and an update of this package was not requested. - symfony/yaml v8.0.8 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement. Problem 5 - 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 6 - 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 7 - 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 8 - 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 9 - 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 10 - nunomaduro/termwind is locked to version v2.4.0 and an update of this package was not requested. - nunomaduro/termwind v2.4.0 requires symfony/console ^7.4.4 || ^8.0.4 -> satisfiable by symfony/console[v8.0.8]. - symfony/console v8.0.8 requires php >=8.4 -> your php version (8.3.30) does not satisfy that requirement.
unit (8.5)
The strategy configuration was canceled because "unit._8_3" failed
unit (8.5)
The operation was canceled.
unit (8.4)
The strategy configuration was canceled because "unit._8_3" failed
unit (8.4)
The operation was canceled.
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/
unit (8.5)
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.4)
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/