- Issue created by @cpigott
- 🇫🇷France sgostanyan
Drupal's update system doesn't treat minor versions (like 6.2.x) as separate upgrade paths—only major versions (6.x, 7.x, etc.) are. So when I released 6.2.0 (for Drupal 11.1+), Drupal saw it as a direct replacement for 6.1.x, even on Drupal 10.3.
To fix this, I’ve reintroduced 6.1.x for 10.3 and moved 6.2.x to a new 7.x branch. Now, if you’re on 10.3, 6.1.x is shown as compatible, and 7.0.0 appears as “also available,” as expected.
Thanks again for raising the issue!