- Issue created by @AaronMcHale
- Assigned to lobsterr
- Status changed to Fixed
almost 2 years ago 10:35pm 4 September 2023 Automatically closed - issue fixed for 2 weeks with no activity.
On Drupal.org, the ggroup version 3.0.0-alpha4 release was created on 3 June 2023 and seems to include everything currently in the 3.0.x branch.
However, the 3.0.0-alpha4 tag in GitLab was created on 15 Sept 2022 (almost a year ago) and so does not contain many of the recent changes that the alpha4 release actually should contain.
This becomes a problem when, after attempting to upgrade to 3.0.0-alpha4 using Composer, it failed because the 11-month-old tag still has the composer.json file requiring group version 2, and we use group version 3.
I would suggest, either: recreate the alpha4 tag in GitLab to point to the same point as the alpha4 release on Drupal.org, or (and this is possibly a better option) tag a new alpha5 release on both GitLab and Drupal.org.
Fixed
3.0
Miscellaneous
Automatically closed - issue fixed for 2 weeks with no activity.