>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3456092. --> Reported by: [acbramley](https://www.drupal.org/user/1036766) Related to !226 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>I started working on a module to replace some deploystacks matrix logic with the new NEXT_MINOR and NEXT_MAJOR work in <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/scheduled_transitions/issues/3456091" title="Status: Closed (fixed)">#3456091: Fix gitlab CI setup to run tests on next major/minor</a></span>. For some reason the NEXT_MAJOR run wasn't running any tests.</p> <p>I tracked this down to how the grep/sed works on the .info.yml file.</p> <p>The module had <code>core_version_requirement: '&gt;=10.3'</code> which did not get parsed correctly by the grep or sed resulting in no tests being run <a href="https://git.drupalcode.org/issue/scheduled_transitions-3456091/-/jobs/1915450">https://git.drupalcode.org/issue/scheduled_transitions-3456091/-/jobs/1915450</a></p> <p>This was not the case for the NEXT_MINOR (because I guess it already supported 10.3)</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <p>Use a constraint that isn't <code>^10</code> in .info.yml and doesn't include <code>^11</code></p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Fix the grep/sed to account for all variations of version constraint, OR just completely replace it with <code>core_version_requriement: ^11</code> - why do we need to shim anything into the existing constraint?</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Agree<br> Do it</p>