No time for upgrading to latest stable release

Created on 23 April 2025, about 1 month ago

Problem

4.0.0 was released today! That's great, but unfortunately there was no time to migrate from the last previous stable 3.* release to the new major. Now 3.x is unsupported already and update-status complains about the unsupported module.

Proposed resolution

Please have a grace period of at least a month to allow people to migrate over to the new major.

πŸ› Bug report
Status

Active

Version

4.0

Component

Miscellaneous

Created by

πŸ‡¦πŸ‡ΉAustria fago Vienna

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @fago
  • πŸ‡³πŸ‡±Netherlands pahles

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

  • πŸ‡ΊπŸ‡ΈUnited States caesius

    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.

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

    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 ;)

  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica
  • πŸ‡©πŸ‡ͺGermany Anybody Porta Westfalica

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

  • πŸ‡¦πŸ‡ΉAustria fago Vienna

    anybody, thank you!

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    Thanks for maintaining this great module, it's simply awesome!

    I also just now saw that composer outdated "drupal/*" shows a new version:

    drupal/field_group 3.6.0 4.0.0 Provides the field_group module.

    To explain what this means even more efficiently, perhaps a section could be added on the project page?

    [...]

    • Html elements

    Version 4 and SemVer

    Field Group is switching to SemVer. Version 4.0.0 is basically a bugfix and feature release of 8.x-3.x. and does not add any backward-incompatible changes, aside from requiring Drupal ^10.3.

    8.x-3.x will be marked unsupported June 2025, please update to version 4 as soon as possible.

    Notes

    • This project will NOT include the multigroup feature [...]

    PS. Regarding false warnings about security updates for versions, which in reality still are safe to use, I am adding a related issue.

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

  • πŸ‡©πŸ‡°Denmark ressa Copenhagen

    @anybody: I still think a section could be added on the project page, to explain what this means even more efficiently. Thanks!

Production build 0.71.5 2024