>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3559325. --> Reported by: [keiserjb](https://www.drupal.org/user/3518715) Related to !12 >>> <p>I have a similar issue to what I faced with ai_search_block. It appears that with the creation of a namespace for ai_search outside of ai, that composer is trying to get a version of ai that does not exist.</p> <p> Problem 1<br> - drupal/ai_related_content[dev-1.0.x, 1.0.0-alpha1, ..., 1.0.x-dev] require drupal/ai_search * -&gt; satisfiable by drupal/ai_search[dev-1.0.x, 1.0.x-dev (alias of dev-1.0.x)].<br> - drupal/ai_search 1.0.x-dev is an alias of drupal/ai_search dev-1.0.x and thus requires it to be installed too.<br> - drupal/ai_search[dev-1.0.x, 1.0.x-dev] require drupal/ai ^2.0 -&gt; found drupal/ai[dev-2.0.x, 2.0.x-dev (alias of dev-2.0.x)] but the package is fixed to 1.2.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.<br> - Root composer.json requires drupal/ai_related_content * -&gt; satisfiable by drupal/ai_related_content[dev-1.0.x, 1.0.0-alpha1, 1.0.0-alpha2, 1.0.x-dev].</p> <p>I've got to move these to custom modules if I want to keep the site updated.</p> > Related issue: [Issue #3558345](https://www.drupal.org/node/3558345)