>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3535731. --> Reported by: [phenaproxima](https://www.drupal.org/user/205645) Related to !604 !580 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Drupal core 11.2.4 will land a few improvements to Package Manager that make it automatically use a copy of Composer packaged locally with the project (i.e., with <code>composer/composer</code> as a dependency). We should absolutely take advantage of these improvements, as they make Package Manager quite a bit easier to get started with.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>When it comes out, require Drupal 11.2.4 or later (<code>^11.2.4</code>) in the project template, along with <code>composer/composer:^2.8</code>. Then roll a new release of <code>drupal/cms</code>. This can go into a patch release of Drupal CMS 1.2.x.</p> <p>Both project templates (the normal one and the cPanel-friendly one) will get the vendor hardening plugin, since core has now made it possible to opt certain packages out of clean-up.</p> > Related issue: [Issue #3534278](https://www.drupal.org/node/3534278) > Related issue: [Issue #3537668](https://www.drupal.org/node/3537668)