Skip to content

feature: resource lock (config not applied for permissions) #59

feature: resource lock (config not applied for permissions)

feature: resource lock (config not applied for permissions) #59

Triggered via push March 20, 2024 23:17
Status Failure
Total duration 11s
Artifacts

php.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
build
Your lock file does not contain a compatible set of packages. Please run composer update. Problem 1 - symfony/css-selector is locked to version v7.0.3 and an update of this package was not requested. - symfony/css-selector v7.0.3 requires php >=8.2 -> your php version (8.1.2) does not satisfy that requirement. Problem 2 - symfony/event-dispatcher is locked to version v7.0.3 and an update of this package was not requested. - symfony/event-dispatcher v7.0.3 requires php >=8.2 -> your php version (8.1.2) does not satisfy that requirement. Problem 3 - symfony/string is locked to version v7.0.4 and an update of this package was not requested. - symfony/string v7.0.4 requires php >=8.2 -> your php version (8.1.2) does not satisfy that requirement. Problem 4 - brianium/paratest is locked to version v7.4.3 and an update of this package was not requested. - brianium/paratest v7.4.3 requires php ~8.2.0 || ~8.3.0 -> your php version (8.1.2) does not satisfy that requirement. Problem 5 - symfony/stopwatch is locked to version v7.0.3 and an update of this package was not requested. - symfony/stopwatch v7.0.3 requires php >=8.2 -> your php version (8.1.2) does not satisfy that requirement. Problem 6 - symfony/string v7.0.4 requires php >=8.2 -> your php version (8.1.2) does not satisfy that requirement. - symfony/console v6.4.4 requires symfony/string ^5.4|^6.0|^7.0 -> satisfiable by symfony/string[v7.0.4]. - symfony/console is locked to version v6.4.4 and an update of this package was not requested.
build
Process completed with exit code 2.
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.