Skip to content
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

Release with composer/xdebug-handler ^3.0? #10528

Closed
wimski opened this issue Feb 9, 2022 · 1 comment
Closed

Release with composer/xdebug-handler ^3.0? #10528

wimski opened this issue Feb 9, 2022 · 1 comment
Milestone

Comments

@wimski
Copy link

wimski commented Feb 9, 2022

I see in the main branch that composer/xdebug-handler ^3.0.1 is supported. When will there be a release with that support?

Currently I have a conflict where one package requires ^3.0 directly and another requires composer/composer ^2.2.4 (with currently ^2 support).

Problem 1
- Root composer.json requires friendsofphp/php-cs-fixer ^3.6 -> satisfiable by friendsofphp/php-cs-fixer[v3.6.0].
- composer/composer[2.2.4, ..., 2.2.6] require composer/xdebug-handler ^2.0 -> satisfiable by composer/xdebug-handler[2.0.0, ..., 2.0.4].
- You can only install one version of a package, so only one of these can be installed: composer/xdebug-handler[1.0.0, ..., 1.4.6, 2.0.0, ..., 2.0.4, 3.0.0, 3.0.1].
- nunomaduro/larastan 2.0.0 requires composer/composer ^2.2.4 -> satisfiable by composer/composer[2.2.4, 2.2.5, 2.2.6].
- friendsofphp/php-cs-fixer v3.6.0 requires composer/xdebug-handler ^3.0 -> satisfiable by composer/xdebug-handler[3.0.0, 3.0.1].
- Root composer.json requires nunomaduro/larastan ^2.0 -> satisfiable by nunomaduro/larastan[2.0.0].
@Seldaek
Copy link
Member

Seldaek commented Feb 16, 2022

I guess I can allow xdebug-handler 3 in the next 2.2 patch release, AFAIK it's compatible as well.

@Seldaek Seldaek added this to the 2.2 milestone Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@Seldaek @wimski and others