Use previous minor version not previous security minor version for "previous minor" variant
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3463708. -->
Reported by: [fjgarlin](https://www.drupal.org/user/2495842)
Related to !383
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>Right now, Drupal 10.2.x is at 10.2.7, but the latest security update was 10.2.2. Sometimes, some changes are backported to the latest 10.2.x, like this one <a href="https://www.drupal.org/node/3437129">https://www.drupal.org/node/3437129</a>, but that's only available in 10.2.7</p>
<p>So, this type of situation just brings the question of "do we need the 'previous minor' variant to be the security one?<br>
Probably the concept of “security” releases is not as important for previous minor, unless you think of it like a LTS sort of thing (ie: people might not update until there is a new “security” release).</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<p>Maybe we could have a simpler CORE_PREVIOUS_MINOR that just has the latest previous minor. We can still keep the old variable in case people reference it, but not use it in the templates.</p>
<p>Note that there is a good deal of logic in the "scripts/check_versions.php" script that would need to be modified.</p>
<h3 id="summary-remaining-tasks">Remaining tasks</h3>
<p>It could be a fix or won't fix, but creating the issue to at least discuss it.</p>
issue