Requirement conflict when upgrading Group module to 2.0beta3

Same here, looking to upgrade a website to D10, so group will have to be upgraded to 2.0. Runnin into the same conflict with composer

2.x supports Group module 1.x. There is a 3.x branch that supports Group 3.x. It would be possible, if someone has the time, to work with the 3.x branch to make a version that supports 2.x (it should largely be a search and replace operation), but at the moment there is no branch of this module that works with Group 2.x.

Just noting what we've done to make this work:

• Updated Domain to D10 compatible version 2.x
• We already have an installation of Group v1.x, so we're forced to update to 2.x.
• Pulled in the not-yet-published D10/Groups 3 compatible branch for Domain Group
• Aliased Group v2.2.1 as 3.0.0 in order to meet Domain Group's constraint

composer require 'drupal/group:2.2.1 as 3.0.0' 'drupal/domain:^2@beta' 'drupal/domain_group:3.x-dev' -W

After the most cursory of testing, things seem to work fine. I suspect we'll eventually need to include the patch from the MR in #7 🐛 Requirement conflict when upgrading Group module to 2.0beta3 Active .

@kerasai Did you continue to use this? Can you confirm that the 3.x compatible version works with 2.x as well? I'll change the dependency if so.

Aside: After all the work to make domain_group 3.x when group_sites came along we've decided it's worth switching to use it. Maintained by the Group module maintainer.

https://www.drupal.org/project/group_sites →