Updating to 3.1 is not possible on Drupal 10.3.x

Hi @KlemenDEV,

I have resolved the version issue and also attached the patch. Please review and verify it.

Drupal version: 10.3.1

Looks good, makes me wonder why there is this version restriction here in the first place. Are you sure we can just remove the restriction?

Yes, I can confirm that after removing the restriction, everything is working as expected.
Also I'm attaching the patch for the same. Thanks.

The patch in #5 🐛 Updating to 3.1 is not possible on Drupal 10.3.x Active works. But 3.0 is unsupported now and upgrading to 3.1 with composer is broken. Time for a 3.2 release.

starting from Drupal 10.3 and above the recommended mail login version is 4.x
check https://www.drupal.org/project/mail_login/issues/3456996 📌 Use UserAuthenticationInterface instead of UserAuthInterface (>=10.3.x) Needs review

4.0.0 is an alpha release. I would not recommend people to install alpha's. So 3.x has to be fixed.

I agree it is a bit harsh to the users having to either use the alpha version or observe error on their status screen that they are using unsupported module when using Drupal 10.3.x

Moreover, 4.x has at least one major issue: https://www.drupal.org/project/mail_login/issues/3456996 📌 Use UserAuthenticationInterface instead of UserAuthInterface (>=10.3.x) Needs review
I upgraded manually to 3.1 with the patch now. Not yet in production, but I will do that when I have tested it on the staging server.

i am on Drupal core 10.2.2 and Mail Login 3.0.
and I get warnings that Mail Login is unsupported.

are there any security concerns with V3.0?
what is the reason for declaring it as unsupported ?

@KlemenDEV
Added v4.0.0 → for Drupal >=10.3
Added v3.0.1 → for Drupal <10.3
and updated the module page information.

There is a critical issue in 4.x now as well: https://www.drupal.org/project/mail_login/issues/3462447 🐛 error logging in with username Active
3.1 with the patch from this issue is working fine.

Mail login v4.0.3 is now released, the reported issues are fixed in the latest 4.0.2 release.