>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3409082. --> Reported by: [fjgarlin](https://www.drupal.org/user/2495842) Related to !100 !99 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>See the parent issue. Tests broke on D7 due to a new release, so we could do some additional checks against the current stable versions and our variables. </p> <p>In fact, we'll need to update a bunch of <code>CORE_*</code> variables next week when 10.2.0 is out... </p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>We could potentially create tests some tests for the gitlab_templates itself and run them as part of the commits/MR checks by adding a new job to the <a href="https://git.drupalcode.org/project/gitlab_templates/-/blob/1.0.x/.gitlab-ci.yml">https://git.drupalcode.org/project/gitlab_templates/-/blob/1.0.x/.gitlab-ci.yml</a> file.</p> <p>The test would be to bring the latest stable for: 7 (7.99 as of last week), 10 (10.1.17 right now, about to change this week), and then compare with <code>CORE_LEG_STABLE</code> and <code>CORE_STABLE</code> and then fail.</p> <p>Latests: <a href="https://www.drupal.org/project/drupal">https://www.drupal.org/project/drupal</a></p> <p>We could target both things in the same issue (the changes and the tests).</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>- [ ] Update variables to recent versions<br> - [ ] Write tests so we can see when this happens on commit/MRs</p> > Related issue: [Issue #3408456](https://www.drupal.org/node/3408456)