Contrib.social

Core Update drama

Open on Drupal.org →
Created on 12 February 2024, 9 months ago
Updated 15 February 2024, 9 months ago

While updating the Drupal core to version 10.2.x in one of our feature branches, I encountered a peculiar issue. The feature branch had previously been on 10.2.x, but I needed to merge our module updates from the development branch into it. Since there were additional changes in the composer.json and composer.lock files, I decided to use both files from the development branch and attempted to reinstall Drush 12 and core-recommended version 10.2.3. However, the installation failed with the following error message:

Your requirements could not be resolved to an installable set of packages.

Problem 1
- Root composer.json requires drupal/core-recommended 10.2.3 -> satisfiable by drupal/core-recommended[10.2.3].
- drupal/core-recommended 10.2.3 requires drupal/core 10.2.3 -> found drupal/core[10.2.3] but these were not loaded, likely because it conflicts with another require.

The Drupal core was stuck at version 10.1.8. Even after running composer why drupal/core, I couldn't identify the problem at first glance. However, while going through the composer.lock file, I found a version constraint in pgtable to ~10.1.0. I remembered that updating pgtable to the latest version introduced a new 2.0.0 version for Drupal 10.2.

The challenge was that the latest version of pgtable dropped support for ^10.x, and our feature branch had been working before merging our development updates with Drupal 10.2.

To upgrade again, I needed to run the following commands:

composer require drupal/core-recommended:10.2.3 drupal/core-composer-scaffold:10.2.3 drupal/core-project-message:10.2.3 'drupal/paragraphs_table:^2.0' -W --no-update

composer update drupal/core-recommended:10.2.3 drupal/core-composer-scaffold:10.2.3 drupal/core-project-message:10.2.3 'drupal/paragraphs_table:^2.0' -W

due to the circle of dependencies.

Maybe there might be a solution to make this process smoother. Or at least, just some warning message on the module page. It took me quite some time to figure out the culprit in this case :-)

✨ Feature request
Status

Active

Version

2.0

Component

Code

Created by

🇩🇪Germany macdev_drupal Wiesbaden

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @macdev_drupal
  • Comment 9 months ago →
    🇩🇪Germany macdev_drupal Wiesbaden
  • Comment 9 months ago →
    🇫🇷France lazzyvn paris

    I really don't see any problem. There are many modules that have to be changed when Drupal 10.2 is released. If I were you I would simply composer remove and composer require again for any module stop support 10.1.x. All modules with field type, field storage settings are affected
    When you update from 10.1.x to 10.2.x, does that mean there is a big change in the core that you must respect? Stop all features in project to 10.1, continue after all up to 10.2. If not, then you probably have a problem with version for the project

  • Comment 9 months ago →
    🇩🇪Germany macdev_drupal Wiesbaden

    Sorry, I think it just messed up things here because we did have 8.x-1.21 running with 10.2 (but not tested yet) and the incoming merge with 8.x-1.22 broke it, and I couldn't figure out the problem, which obviously should have something to do with one of the updated modules.
    You are right.
    Maybe it's better to do it like what we did when upgrading from D9 to D10 like here: "drupal/csv_serialization": "4.0 as 3.0".
    This will make composer.json merge conflicts easier to handle if other modules will follow to lock support.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024