Drupal 12 environment requirements are not yet defined, don't use Drupal 10 requirements

Thanks, great to see that Drupal 12 is in the pipeline :)

It looks like the new version makes all tests fail, since projects don't yet have || ^12 in composer.json or projectname.info.yml, see for example this test:

https://git.drupalcode.org/issue/masquerade-3158235/-/jobs/5136316

To allow the control to pass, I need to add || ^12 in the two files:

$ drush upgrade_status:analyze masquerade
 [notice] Processing /var/www/html/web/modules/contrib/masquerade.

================================================================================
Masquerade,  8.x-2.0
Scanned on Fri, 2 May 2025 - 21:31

No known issues found.

Otherwise, the test fails:

$ drush upgrade_status:analyze masquerade
 [notice] Processing /var/www/html/web/modules/contrib/masquerade.

================================================================================
Masquerade,  8.x-2.0
Scanned on Fri, 2 May 2025 - 21:32

FILE: web/modules/contrib/masquerade/masquerade.info.yml

STATUS         LINE                           MESSAGE                           
--------------------------------------------------------------------------------
Check manually 4    Value of core_version_requirement: ^9.2 || ^10.2 || ^11.0 is
                    not compatible with the next major version of Drupal core.  
                    See https://drupal.org/node/3070687.                        
--------------------------------------------------------------------------------

FILE: web/modules/contrib/masquerade/composer.json

STATUS         LINE                           MESSAGE                           
--------------------------------------------------------------------------------
Check manually 1    The drupal/core requirement is not compatible with the next 
                    major version of Drupal. Either remove it or update it to be
                    compatible. See                                             
                    https://www.drupal.org/docs/develop/using-composer/add-a-com
                    poserjson-file#core-compatibility.                          
--------------------------------------------------------------------------------

Or ... perhaps the individual project maintainers themselves toggle the Upgrade Status test?