- Issue created by @nicxvan
- 🇭🇺Hungary Gábor Hojtsy Hungary
Right, it does say it is not compatible though, true?
Looks like our code only checks the very latest release and judges by that. It could be more elaborate and scan through the list of releases if there was one that is Drupal 11 compatible. Then it would need some kind of constraint resolution logic though as to what it suggests, etc.
See https://git.drupalcode.org/project/upgrade_status/-/blob/4.x/src/Project...
- 🇭🇺Hungary Gábor Hojtsy Hungary
Or it could go backwards until it finds one compatible release and suggest that instead of the last one. I guess that would still be better.
- 🇭🇺Hungary Gábor Hojtsy Hungary
I don't have capacity ATM to do this, but added a todo to where it needs work :)
- 🇺🇸United States nicxvan
It also doesn't check the current version.
After I updated rabbit hole to the 1.0.0 which is Drupal 11 compatible it still shows as needing work.
- 🇭🇺Hungary Gábor Hojtsy Hungary
That's strange. Did you run the update status check at the top? What kind of issues does it report with 1.0.0?
- 🇺🇸United States nicxvan
Ok after clearing cache it is now in the compatible with the next version, but it says to install 2.x which is incompatible.
I uploaded a screenshot.
Before updating to 1.0.0 it said it required an update and recommended 2.x which is incompatible rather than 1.0.0 which is compatible.
- 🇺🇸United States nicxvan
Ok I downgraded to the beta11.
Rabbit hole shows up in the upgrade list. I uploaded a screenshot.
It says it is incompatible and recommends 2.x rather than 1.0.0