No time for upgrading to latest stable release

I concur, why was 8-3.6 marked unsupported already?

I'm gonna go on a limb and say that 4.0.0 probably does not add any BC-incompatible changes aside from requiring Drupal ^10.3, in which case it's not much different from just updating to a theoretical 8.x-3.7 release (and that versioning scheme has been bugging me for a while 🐛 Field Group 3.5 WSODs on Drupal <=10.2 Fixed , personally).

Also, is the update module complaining about unsupported-ness on a production site? It's best to leave it disabled on production so as not to scare clients every time a security update releases.

Hi @fago, @caesius is right, while this is a major version change, there were no breaking changes and requiring ^10.3 (which is actually the supported release besides ^11) is the only relevant change.

Nonetheless, I totally understand your point, and we marked 3.x as supported for some more weeks, this was probably a bit too fast ;)

I also clarified that in the release notes and the short description now, thanks for your hint!

anybody, thank you!