Skip to content

Run thunder-develop tests #221

Run thunder-develop tests

Run thunder-develop tests #221

Triggered via schedule September 12, 2024 07:19
Status Success
Total duration 4m 27s
Artifacts

tests.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
test
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.4 (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.4 (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.4 (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.4 (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.8 requires drupal/core 10.2.8 -> found drupal/core[10.2.8] but the package is fixed to 10.3.4 (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.8]. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
test
Scaffold file assets/scaffold/files/editorconfig not found in package drupal/core.
test
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/
test
The following actions use a deprecated Node.js version 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/