- Issue created by @dpi
- @dpi opened merge request.
- @dpi opened merge request.
Automatically closed - issue fixed for 2 weeks with no activity.
- 🇺🇸United States loopy1492
Interesting. Switching to >=10 means this can't be updated until someone actually updates their site to Drupal 10.
- 🇦🇺Australia dpi Perth, Australia
Per project page:
2.x is compatible with Drupal 10 and above. The branch is feature and config compatible with 8.x-1.x and is thusly a drop-in replacement.
If it helps, you can set your constraints to
^1 || ^2and you'll get the upgrade automatically when you upgrade to Drupal 10, with the usual -w flag, just like you'll get numerous other [non root] dependencies when you upgrade to D10. - 🇳🇱Netherlands Heine
Not having an overlapping D9/D10 release means that users upgrading with the help of upgrade_status are not able to get a "green" board on D9. They have to track these updates manually.
