[#47] Update Distro to v10.3.10 (and subdependencies)
Check list to complete before assigning a MR to someone:
-
Link related issues on Related Issues
; -
Update documentation; -
Comment relevant changes, why/what lead us to make this change; -
Review at least once you own MR; -
Tests green;
Related issues:
Merge request reports
Activity
added In progress label
assigned to @cpetala
Hi Christina, I see we have 10.3.2 already: !239 (closed)
and we can take the chance to bump some other dependencies as well:
I suggest we prepare a merge request including all upgrades we possible can and create a website for the Web team to test. @ldelpian the patches will likely need to be reviewed after, some may not be relevant anymore
- Resolved by Carina Antunes
Hi @crdeoliv,
So we should bump to 10.3.2, right?
The first attempt to upgrade to 10.3.0 has some issues. It was performed with composer commands as follows:
# composer require drupal/core-recommended:10.3.0 --update-with-dependencies # composer require drupal/core-composer-scaffold:10.3.0 --update-with-all-dependencies # composer require drupal/core-project-message:10.3.0 --update-with-all-dependencies
but in any case this resulted in updating only the versions of the know components:
"drupal/core-composer-scaffold": "10.3.0", "drupal/core-project-message": "10.3.0", "drupal/core-recommended": "10.3.0",
During the execution of the composer commands I got this:
And after applying the newly created image into a test site (https://home-ckeditor.webtest.cern.ch/) on drupal-stg:
drush updb
I believe that indeed there is an issue with the patches but I will need to investigate further.
I can see https://www.drupal.org/project/drupal/releases/10.3.6 released on October so most propably we should bump to this version.
changed title from Draft: [#47 (closed)] Update Distro to v10.3.0 to Draft: [#47 (closed)] Update Distro to v10.3.6
changed title from Draft: [#47 (closed)] Update Distro to v10.3.6 to Draft: [#47 (closed)] Update Distro to v10.3.7
Dear @jyde ,this is the comment I was reffering too during our standup today. Thank you!
Below are the details of the changes made in this MR, which I believe the web team should consider during testing:
- "drupal/aggregator": "2.2.2" was removed due to the error:
- Only one of these can be installed: drupal/core[8.0.0-beta12, ..., 8.9.x-dev, 9.0.0-alpha1, ..., 9.4.3, 10.0.0-alpha1, 10.0.0-alpha2], drupal/aggregator[2.2.2]. drupal/core replaces drupal/aggregator and thus cannot coexist with it. 177 - drupal/core[9.0.0-alpha1, ..., 9.0.0-alpha2] require symfony/psr-http-message-bridge ^1.2.0 -> satisfiable by symfony/psr-http-message-bridge[v1.2.0, v1.3.0]. 178 - drupal/core[8.7.8, ..., 8.9.10] require symfony/psr-http-message-bridge ^1.1.2 -> satisfiable by symfony/psr-http-message-bridge[v1.1.2, 1.1.x-dev, v1.2.0, v1.3.0]. 179 - drupal/core[8.8.0-alpha1, ..., 8.8.x-dev] require zendframework/zend-feed ^2.12 -> satisfiable by laminas/laminas-feed[2.12.0, ..., 2.24.x-dev], zendframework/zend-feed[2.12.0, 2.12.x-dev, 2.13.x-dev]. 180 - Root composer.json requires drupal/viewsreference 2.0.0-beta1 -> satisfiable by drupal/viewsreference[2.0.0-beta1]. 181error building image: error building stage: failed to execute command: waiting for process to exit: exit status 2
-
"drupal/viewsreference": "dev-1.x" could not be upgraded due to errors - remained in dev-1
-
All other modules were upgraded to the latest versions based on !265.
fyi @crdeoliv
Edited by Christina Petalamentioned in merge request !268
- Resolved by Carina Antunes