Skip to content

Run thunder-develop tests #361

Run thunder-develop tests

Run thunder-develop tests #361

Triggered via schedule May 17, 2025 07:21
Status Success
Total duration 6m 54s
Artifacts

test.yml

on: schedule
Fit to window
Zoom out
Zoom in

Annotations

2 errors
test
Scaffold file assets/scaffold/files/htaccess not found in package drupal/core.
test
Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires drupal/core-recommended ~11.1.0 -> satisfiable by drupal/core-recommended[11.1.0-beta1, ..., 11.1.x-dev]. - drupal/core-recommended 11.1.0-rc1 requires drupal/core 11.1.0-rc1 -> found drupal/core[11.1.0-rc1] but the package is fixed to 11.1.7 (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 11.1.0-beta1 requires drupal/core 11.1.0-beta1 -> found drupal/core[11.1.0-beta1] but the package is fixed to 11.1.7 (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 11.1.0 requires drupal/core 11.1.0 -> found drupal/core[11.1.0] but the package is fixed to 11.1.7 (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 11.1.1 requires drupal/core 11.1.1 -> found drupal/core[11.1.1] but the package is fixed to 11.1.7 (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 11.1.2 requires drupal/core 11.1.2 -> found drupal/core[11.1.2] but the package is fixed to 11.1.7 (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 11.1.3 requires drupal/core 11.1.3 -> found drupal/core[11.1.3] but the package is fixed to 11.1.7 (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 11.1.4 requires drupal/core 11.1.4 -> found drupal/core[11.1.4] but the package is fixed to 11.1.7 (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 11.1.5 requires drupal/core 11.1.5 -> found drupal/core[11.1.5] but the package is fixed to 11.1.7 (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 11.1.6 requires drupal/core 11.1.6 -> found drupal/core[11.1.6] but the package is fixed to 11.1.7 (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 11.1.7 requires asm89/stack-cors ~v2.2.0 -> found asm89/stack-cors[dev-master, v2.2.0, 2.2.x-dev (alias of dev-master)] but the package is fixed to v2.3.0 (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 11.1.x-dev requires drupal/core 11.1.x-dev -> found drupal/core[11.1.x-dev] but the package is fixed to 11.1.7 (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. Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.