>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3487864. --> Reported by: [megakeegman](https://www.drupal.org/user/3620027) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>I did not want to create this issue because everything looks like it has been done the way it should. I am trying to get to the latest version of Drupal 9, so I can upgrade to Drupal 10. For some mysterious reason, composer is resolving this module to the beta1 release (backwards from rc1 which was the last version installed), which does not work. The only place I am requiring this module is in the root composer.json of my project, where I have set</p> <pre>"minimum-stability": "dev",<br>"prefer-stable": true,</pre><p>Okay so that's strange, but then I try to upgrade to the latest RC release: <a href="https://www.drupal.org/project/custom_book_block/releases/1.0.0-rc2">https://www.drupal.org/project/custom_book_block/releases/1.0.0-rc2</a><br> or straight to 1.0.x-dev</p> <p>Now is when I learn what composer is really thinking:</p> <pre>...<br>- drupal/custom_book_block dev-1.0.x requires drupal/book * -&gt; satisfiable by drupal/book[dev-1.0.x, dev-2.0.x, 1.0.0, 1.0.x-dev, 2.0.0-alpha1, ..., 2.0.x-dev], drupal/core[8.0.0-beta8, ..., 8.9.x-dev, 9.0.0-alpha1, ...,9.4.3, 10.0.0-alpha1, ..., 10.0.0-alpha6].<br>- drupal/book[dev-1.0.x, 1.0.0, ..., 1.0.x-dev] require drupal/core &gt;=10.0 -&gt; satisfiable by drupal/core[10.0.0-alpha1, ..., 10.5.x-dev, 11.0.0-alpha1, ..., 11.x-dev].<br>- drupal/book[dev-2.0.x, 2.0.0-alpha1, ..., 2.0.x-dev] require drupal/core ^10.3 || ^11 -&gt; satisfiable by drupal/core[10.3.0-beta1, ..., 10.5.x-dev, 11.0.0-alpha1, ..., 11.x-dev].<br>...</pre><p>Now I looked in the 1.0.x-dev composer.json, and it most certainly does not require the contrib book module, and same for the RC release. I am really not sure why composer thinks this. I tried deleting my lock file. I tried deleting all of vendor, core, and contrib. There is something I am not seeing.</p> <p>I checked composer why:</p> <pre>ddev composer why drupal/custom_book_block<br>my_project/my_project dev-main requires drupal/custom_book_block (^1)</pre><h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>This is not a permanent resolution. But I got around this issue by creating a patch that was a diff between the 1.0.x branch and the beta1 branch, and just applying it. Everything seems happy. I thought I would document this in case anyone else comes across this strange issue. And perhaps there is a better solution that I am just not seeing.</p>