- Issue created by @mpotter
- 🇺🇸United States mpotter
Hrm, I can see where this would be problematic given that upgrade_status is using the @deprecated flag to determine problems, and if the site is already in D10 those things have already been removed. So it has nothing to test against.
So probably no way to do this. I guess we really just need to stress to sites to scan modules on their D9 site first and not just edit their custom module info.yml files to D10 thinking it can be scanned later.
- Status changed to Fixed
2 months ago 8:20am 8 July 2024 - 🇭🇺Hungary Gábor Hojtsy Hungary
Right you explained it yourself why this is not possible :) Added this to the project page now to make this clearer:
You must run compatibility checks on your current site against the next major version (ie. on a Drupal 10 site for Drupal 11 compatibility). It is not possible to run most compatibility checks on an upgraded site (ie. once you upgraded to Drupal 11), because the deprecated APIs, libraries, etc. are not present anymore.
Automatically closed - issue fixed for 2 weeks with no activity.