Request to release 1.21

Given there is an automated update path to maintain the status quo I would really prefer that people use the Drupal 11 release as an opportunity to upgrade so I am not maintaining two versions in parallel without any feature reason to do so.

If there are any issues you are having with the 2x version, could you raise those seperately please?

Of course I fully understand.

I have not tested yet the transition to the 2.x version, but if it is ready for production use, then it could be retagged to rc1 or similar, as currently it is still tagged as an alpha, and it seemed to me that maybe it is too early to switch.

While 1.x really just required a new tag, which is why I requested.

But then I will run some tests on the 2.x branch soon to see.

Yeah I should switch it really, it's in use by currently 600 sites already according to announced stats (which is just a portion of real use I believe) and we use it ourselves at my agency on 2x of course. Rare issue raised but seems mostly feature request (1 issue raised with tokens I haven't explored yet). Test coverage is also better which helps maintenance. Will try to get to taking it out of alpha this week.

Having the dev version let's people install it if they really want in Drupal 11 upgrade without having to eg use composer lenient but need some trigger to encourage updating so it doesn't go on forever.

In any case thanks for your understanding.

Thanks!

It seems to work.

Not sure if it is only due the upgrade,
but for me the site settings content list (admin/content/site-settings) did not list the Type only the Group and listed all translations, which looked a bit weird.
But since it is a view I was able to easily modify it.
I got Deprecated function: mb_strtolower() when saving the views, but as far as I see that could be a Core issue and not related to the module.

Thanks for the feedback!

1. No use of mb_strtolower() in the code, so must be unrelated to here.
2. Raised 📌 Show type in site settings list by default Active