-
-
Notifications
You must be signed in to change notification settings - Fork 239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make compatible with Composer 2 #313
Comments
see also #309 definitely in favor of this. |
Oh dang. I missed that when I searched for an existing issue because I wasn't searching PRs (shakes fist at github defaults). Perhaps we should leave this open then for others who might do the same. Thanks. |
When do you plan to release a new version with Composer 2.x support? As I can see it is only available in |
Hm, and why |
I would also like compatibility with Composer 2. Do we have an idea when this is likely to happen? |
If I'm not mistaken this was added in #321 Can we get a new stable release so end users can start using Composer 2? |
@danepowell, we would also need #330 to go in before this works with composer 2. |
you could already beta-test composer v2 support with a constraint like
one issue we ran into when using the plugin with composer-v2 is
for a first step I just added some automation using phpstan and phpunit run by a github action would love to get some support to hunt down remainig problems on the road to composer v2 support |
@clxmstaab I believe that issue is addressed in PR #330. |
As of 1.7.0, this is fixed. Thanks! |
Drupal aims to be compatible with Composer 2. See Issue #3126566.
As one of the most widely used plugins in Drupal, we should aim to make this plugin compatible with Composer 2 too.
The text was updated successfully, but these errors were encountered: