Is this being maintaned?

Seeking co-maintainer(s) but yes, it will be maintained when i receive help from community, thanks!

Hope you can create another issue offering yourself as a co-mantainer, response to this issue title is solved ;)

New maintainer on duty here.

I didn't have this module under my radar, now I have it, I think I can upgrade it soon.

Magic, thanks @tunic → !

Happy to test out anything you come up.

Hi @sirclickalot, the patch to upgrade is here: 💬 Drupal 11 release for this? Active

I will help me a lot if you provide feedback there.

Thanks!

Thanks @tunic,

I have applied the patches from #3498382: Drupal 11 release and the following files have been adjusted and all look correct to me.

Apologies if I am being a bit dim here but I still cannot seem to get Field Group itself up to 4.x.

My site composer.json reads (actual versions loaded in brackets)...

...
"drupal/popup_field_group": "^1.9" (1.9.0)
"drupal/field_group_label": "^2.0" (2.0.0)
"drupal/field_group": "^3.4.0" (3.6.0)
...

But when then go to update using ...

composer require 'drupal/field_group:^4.0'

I am still getting the same response...

Problem 1
    - Root composer.json requires drupal/field_group ^4.0, found drupal/field_group[dev-4.x, 4.0.0-alpha1, 4.0.0, 4.x-dev] but these were not loaded, likely because it conflicts with another require.
  Problem 2
    - drupal/field_group_label is locked to version 2.0.0 and an update of this package was not requested.
    - drupal/field_group_label 2.0.0 requires drupal/field_group ^3.4 -> found drupal/field_group[dev-3.x, 3.4.0, 3.5.0, 3.6.0, 3.x-dev (alias of dev-3.x)] but it conflicts with your root composer.json require (^4.0).
  Problem 3
    - drupal/popup_field_group is locked to version 1.9.0 and an update of this package was not requested.
    - drupal/popup_field_group 1.9.0 requires drupal/field_group * -> found drupal/field_group[dev-1.x, dev-3.x, dev-4.x, 1.0.0-rc3, ..., 1.x-dev (alias of dev-1.x), 3.0.0-beta1, ..., 3.x-dev (alias of dev-3.x), 4.0.0-alpha1, 4.0.0, 4.x-dev] but these were not loaded, likely because it conflicts with another require.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

I am never very confident with composer when this type of thing happens but I think your update in from f9fc36cf really should have done it for me.

I would say it is because composer is using the module without taking into account the composer.json of the module. This makes sense because that composer.json file is, as far as I know, for Packagist, not for the local composer.

Once there is a release of this module composer will be able to solve the issue.

My idea is wait a few days, maybe next week, to receive feedback from other users, then publish a new release.

If no feedback is received I will publish the release anyway, as the new code worked ok on your site.

Ah OK, thanks for that @tunic

I think I get that; so when do an actual composer require <next release> it'll work.

Thanks again - it's such a useful module.

Humble addition to this magic dance, new "beta" release up to avoid these kind of blocking composer dichotomies.

Try https://www.drupal.org/project/field_group_label/releases/2.1.0-beta1 → by:
composer require 'drupal/field_group_label:^2.1@beta'

Don't forget to include "-w, --with-dependencies" if it is required.

Other "2.0.0" still is the stable release, 2.1.0 will replace that one when https://www.drupal.org/project/field_group_label/issues/3498382 💬 Drupal 11 release for this? Active is fixed, fruther any related question and not related with your specific need, please, note to that one. Any new feedback or possible pending adjustment.

Thanks both! Really needed help with this one.

Final note: both releases visibles into main module page & mantained ;)

Thank you enormously @crzdev

I can can confirm that 2.1.0.-beta-1 all works as expected; it UNblocks the Field Group update to 4.x and I have updated #3498382 💬 Drupal 11 release for this? Active to say so.