- Issue created by @caesius
- π¬π§United Kingdom scott_euser
See comment at https://www.drupal.org/project/field_group/issues/3456987#comment-15711152 π Fix deprecated extending of render element Fixed - probably easiest way to solve is to prevent upgrading just the module yet locking in to old version of core.
- πΊπΈUnited States caesius
Simply updating the version constraint would not resolve the issue or change the workaround, which currently is to explicitly composer require drupal/field_group:3.4.0
If requiring field_group:^3 then Drupal 10.2 sites would still try to update to the bad 3.5 version as it's the latest 3.x that is listed as compatible with 10.2. There is no way to go back and apply a constraint to the current 3.5 version.
Fixing this absolutely requires that π Fix deprecated extending of render element Fixed be either reverted or made backward compatible on 3.x. If it can't be made backward compatible then 3.5 can be rereleased as 4.0.0 with version constraints so they have something to run automated tests on without them failing.
This is also an opportunity to update to proper semantic semantic versioning as this module still uses the old 8.x-X.Y format instead of the modern X.Y.Z
- Status changed to Fixed
9 months ago 8:09am 3 August 2024 - π§πͺBelgium nils.destoop
I temporarily reverted #3456987 and created a new release
Automatically closed - issue fixed for 2 weeks with no activity.