Mark versions 3 and 4 to only support Drupal core 11.1 or below

@jurgenhaas sounds like a plan

Updated summary with link to issue with reason as to why this has happened.

Small suggestion for the future: when releasing a new minor version of a module, could you leave the old version as supported for a few weeks to give people time to update? When the old versions are immediately labeled as unsupported when a new minor release is made, it does not give maintainers an opportunity to update to the supported version.

For people with Update Status module enabled, it can cause confusion / concern with stakeholders that believe abandoned / insecure modules are in-use on their websites.

Thanks for all the hard work on Gin!

Thank you @kmonty for commenting. We usually do exactly that, but this time it wasn't possible. The constraint on Drupal core was defined as ^11 which would allo version 4.0 to be installed on Drupal 11.2, but it's not compatible with it. Therefore, we had to create 4.1 which makes it clear that it only works with Drupal below 11.2, and 4.0 to be unsupported. There is no difference between the latest 4.0.6 release and 4.1.0, so updating comes with no risk.

Automatically closed - issue fixed for 2 weeks with no activity.