Problem/Motivation

I have

"drupal/core-composer-scaffold": "10.6.*@stable",
"drupal/core-recommended": "10.6.*@stable",

But only the scaffold was updated to the latest release after running composer update -W

There was no dependency conflict or anything. I'm wondering if this is something related to #3612448: Widen constraints in core-recommended for 11.3.x and 10.6.x that was merged.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

Comments

solideogloria created an issue. See original summary.

solideogloria’s picture

solideogloria commented
Related issues: +#3612448: Widen constraints in core-recommended for 11.3.x and 10.6.x
cilefen’s picture

cilefen commented
Category: Bug report » Support request

A 10.6.* is insufficient to force an upgrade to any specific 10.6 version. That on its own, isn't a bug.

cilefen’s picture

cilefen commented

composer why-not drupal/core 10.6.15 will give you technical information as to what is preventing upgrading.

solideogloria’s picture

solideogloria commented 
$ ddev composer why-not drupal/core 10.6.15 
drupal/core-recommended    10.6.14    requires         drupal/core (10.6.14)                
drupal/core                10.6.15    requires         twig/twig (^3.28.0)                  
drupal/recommended-project dev-master does not require twig/twig (but v3.27.1 is installed) 
Not finding what you were looking for? Try calling `composer update "drupal/core:10.6.15" --dry-run` to get another view on the problem.
Composer [why-not drupal/core 10.6.15] failed, composer command failed: exit status 1. stderr=
cilefen’s picture

cilefen commented

What does the recommended --dry-run flag produce?

solideogloria’s picture

solideogloria commented

This looks specifically like it's related to that issue I mentioned.

solideogloria’s picture

solideogloria commented 
$ ddev composer update "drupal/core-recommended:10.6.15" --dry-run -W
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - drupal/recommended-project is present at version dev-master and cannot be modified by Composer
    - Root composer.json requires drupal/core-recommended 10.6.*@stable -> satisfiable by drupal/core-recommended[10.6.15].
    - drupal/core-recommended 10.6.15 requires drupal/core 10.6.15 -> satisfiable by drupal/core[10.6.15].
    - drupal/core[10.6.15] cannot be installed as that would require removing drupal/recommended-project[dev-master]. They both replace drupal/history and thus cannot coexist.

Not sure why it says drupal/recommended-project[dev-master] is installed...

solideogloria’s picture

solideogloria commented

My composer.json has "name": "drupal/recommended-project", at the top. ChatGPT says this causes the error, but this is typical for a project created from the Drupal recommended-project template. It hasn't caused any issue until now.

EDIT: changing the project name did not remove the error.

solideogloria’s picture

solideogloria commented
Status: Active » Fixed

I had to remove 

    "replace": {
        "drupal/history": "*"
    },

These workarounds are really annoying to keep track of. Hopefully we won't need to do that anymore.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.