-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Support Composer 2 #33
Comments
I have not yet had the opportunity to look in more detail the version 2.0 of Composer. Is it just a matter of version constraint? Or, are there more problematic changes for this plugin? |
The interface has changed, see https://github.com/composer/composer/blob/master/UPGRADE-2.0.md#upgrades-guides-for-composer-1x-to-20 |
Looks like the following would work:
public function deactivate(Composer $composer, IOInterface $io): void
{
// do nothing
}
public function uninstall(Composer $composer, IOInterface $io): void
{
// do nothing
}
|
@samdark Thank you! I will try to find some time this weekend to test the compatibility with Composer v2. |
Compatibility added by b7473e7. |
Interesting. Composer 2 fails to install it:
|
You can try with https://github.com/yiisoft/yii-bootstrap4 |
Sure enough, I also get this error now. |
My test was with the master branch and not with a compiled version of Composer. This comes from checking the version of Composer which is a SHA1 and not I add this case right away. |
Compatibility with Composer snapshots added by 201420a. |
Works now. Thank you! |
composer-plugin-api
for upcoming Composer 2 (can be installed withcomposer self-update --snapshot
) has version 2.0.0.The foxy/foxy package requires
composer-plugin-api
version 1.0.0 thus can't be used with Composer 2.The text was updated successfully, but these errors were encountered: