Module reported not compatible with Drupal 10.5.1

Confirming this is an issue.

Are there any changes to the code that preclude version 10 compatibility completely?

sadashiv → changed the visibility of the branch 3537435-module-reported-not to hidden.

Changing the version to 3.1 as 3.2 is compatible only with drupal 11.

sadashiv → changed the visibility of the branch 3537435-module-reported-not to active.

sadashiv → changed the visibility of the branch 3537435-module-reported-not to hidden.

sadashiv → closed merge request !42

Still an issue with Drupal Core 10.5.3.

I tried to check in the core and see that this is not a problem as we are on the update page it means the new version which is available is not compatible with the current drupal installation i.e. the module has a new version which is supported only by drupal 11 and is not compatible with 10.5, this doesn't mean there is a problem with current version.

My pr is just a syntax improvement.

Thanks,
Sadashiv.

It is incorrectly reporting that the module needs to be updated. If the site is Drupal 10.5.3, the module should not register that an update is needed. Only 3.1 is compatible with Drupal 10 and that is what we have installed. If we follow the guidance and update to 3.2, it will cause problems, so there is definitely something wrong that needs to be addressed.