Allow installing modules on next major that have a drupal/core dependency in their composer.json
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3437131. --> Reported by: [berdir](https://www.drupal.org/user/214652) Related to !167 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>See <a href="https://git.drupalcode.org/project/redirect/-/jobs/1196104">https://git.drupalcode.org/project/redirect/-/jobs/1196104</a></p> <p>redirect composer.json currently require drupal/core 9 or 10 explicitly. That causes the current next major composer build step to fail as it results in an invalid combination of drupal/core dependencies.</p> <p>It tries to fix that by removing drupal/core-recommended if drupal/core exists in require-dev, but I think that's the wrong approach and a leftover of the drupalspoons script which didn't support anything like next/previous major.</p> <p>CI should define and enforce the used core version depending on the job, so I think a better fix would be to ignore any drupal/core requirement</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3 id="summary-ui-changes">User interface changes</h3> <h3 id="summary-api-changes">API changes</h3> <h3 id="summary-data-model-changes">Data model changes</h3> > Related issue: [Issue #3414505](https://www.drupal.org/node/3414505)
issue