Update ddev configuration #143
Annotations
2 errors and 2 warnings
Your requirements could not be resolved to an installable set of packages.
Problem 1
- drupal/core-recommended 10.2.4 requires drupal/core 10.2.4 -> found drupal/core[10.2.4] but the package is fixed to 10.3.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/core-recommended 10.2.5 requires drupal/core 10.2.5 -> found drupal/core[10.2.5] but the package is fixed to 10.3.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/core-recommended 10.2.6 requires drupal/core 10.2.6 -> found drupal/core[10.2.6] but the package is fixed to 10.3.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/core-recommended 10.2.7 requires drupal/core 10.2.7 -> found drupal/core[10.2.7] but the package is fixed to 10.3.1 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires drupal/core-recommended ~10.2.4@stable -> satisfiable by drupal/core-recommended[10.2.4, 10.2.5, 10.2.6, 10.2.7].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
|
|
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 following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
This job succeeded
Loading