>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3523047. --> Reported by: [gábor hojtsy](https://www.drupal.org/user/4166) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Drupal 12 will be release June 2026 according to plans. We would like to make Drupal CMS modules compatible as soon as possible, which would need an understanding of readiness. Also it would be good to know this for tooling development in time. So it would be great to start running readiness checks. Currently with 11.x, later with Drupal 12 :) </p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <ol> <li>Make a new branch, master-12 and results-d12.</li> <li>Adjust <code>project_analysis_utils/bin/process_projects</code> to filter to Drupal 11.2 compatible projects.</li> <li>Adjust the installer to install d11.2 and run from that. Make sure we run on proper php images.</li> <li>Adjust rector.php to make as much sense as possible, we should probably drop d8/d9 rectors by now.</li> <li>Make new drupal 12 issue tag.</li> <li>Adjust issue templates and such for d12 readiness.</li> <li>Start running against those projects.</li> </ol> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ol> <li>Child issue for rector 2.0 in drupal-rector, its close to being merged, but still: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/rector/issues/3493467" title="Status: Closed (fixed)">#3493467: Update drupal-rector to rector 2.0</a></span></li> <li>Local tasks from the solution </li> </ol> <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>