>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3492516. --> Reported by: [bbholty1](https://www.drupal.org/user/3835881) >>> <h2>Drupal version</h2> <p>11</p> <h2>Drupal Rector version</h2> <p>1.2.10</p> <h2>Problem / Motivation</h2> <p>I'm a Drupal Noob and Drupal 11 is my first sight install.<br> There's several Drupal Modules I'm interested in installing which currently only support up to V 10 of Drupal.<br> I used the lenient module to get these modules installed using composer require.<br> So now I can see the modules in my list of modules stating what I expected: This version is not compatible with Drupal 11.0.9 and should be replaced.</p> <p>So my expectation now was to use rector to take a shot at fixing the compatibility issues between Drupal 10 and 11 on these modules.<br> I followed all the steps in the rector github README including copying the vendor/palantirnet/drupal-rector/rector.php to the proper location.</p> <p>When I ran vendor/bin/rector process --dry-run on the first deprecated module, I saw 13 files being process, but it didn't output any diff of any changes.<br> And just for kicks I ran the same command without the --dry-run and nothing changed in the module.</p> <p>According to the rector home page it states: Rector can save you a lot of manual work by automating code upgrades to Drupal 9, 10 and 11.</p> <p>So any help in how I can get this to work on Drupal 11 would be greatly appreciated!</p> <p>Thanks in advance!<br> -Bryan Holty</p>