- Issue created by @dimaro
- 🇪🇸Spain lluvigne Seville, Spain
cspitzlay → credited lluvigne → .
-
cspitzlay →
committed 35c3629e on 2.0.x
Issue #3502313 by dimaro, lluvigne, cspitzlay: Support Commerce 3.x
-
cspitzlay →
committed 35c3629e on 2.0.x
- 🇩🇪Germany cspitzlay 🇩🇪🇪🇺
Thanks for your contribution!
I created a new branch "2.0.x" for support of D11 and Commerce 3.x.
I removed D11 support from the 1.0.x info.yml so it reflects the reality.I reviewed and committed your changes, so you should soon have them in a dev snapshot.
I haven't tested them yet, though, so I'm leaving the issue open for now. - 🇩🇪Germany gruberroland
As Commerce 3 is supported on Drupal 10, can you keep Drupal 10 as supported for 2.0.x (and only require Commerce 3.x)?
- 🇩🇪Germany cspitzlay 🇩🇪🇪🇺
The dev snapshot 2.0.x-dev is now available. I also updated the project page and created the release 1.0.0-alpha6 which dropped the claim of D11 support.
- 🇩🇪Germany cspitzlay 🇩🇪🇪🇺
As Commerce 3 is supported on Drupal 10, can you keep Drupal 10 as supported for 2.0.x (and only require Commerce 3.x)?
Yes, if that's the case then I can re-add D10 in the 2.0.x branch.
- 🇩🇪Germany gruberroland
Thanks a lot, will test 2.0.x the next few days on Drupal 10.
- 🇩🇪Germany gruberroland
I was able to create successful orders with Drupal 10 + Commerce 3 with the 2.0.x branch. Both on site and off site.
- 🇩🇪Germany cspitzlay 🇩🇪🇪🇺
I created an alpha release for the 2.0.x branch.
Automatically closed - issue fixed for 2 weeks with no activity.