-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Labels
enhancementNew feature or requestNew feature or request
Description
My feature title
Support rector ^2.0
Background/problem
I already updated some repos to rector ^2.0, but when I wanted to add this package as a library it failed at runtime due to incompatibilities (no idea why composer even let me install it, since the dependency constraints are invalid).
Proposal/solution
Upgrade to rector ^2.0.
Currently this is blocked by ramsey/devtools because of a dependency on phpstan.
Also rector should be moved from require-dev to require since it is used at runtime.
Alternatives
We can probably move ramsey/devtools to vendor-bin to avoid these conflicts, since ramsey/devtools doesn't seem to be used at runtime.
Additional context
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires ramsey/devtools ^2.0 -> satisfiable by ramsey/devtools[2.0.0].
- Root composer.json requires rector/rector ^2.0 -> satisfiable by rector/rector[2.0.0-rc1, ..., 2.0.7].
- rector/rector[2.0.0-rc1, ..., 2.0.3] require phpstan/phpstan ^2.0.1 -> satisfiable by phpstan/phpstan[2.0.1, ..., 2.1.x-dev].
- rector/rector 2.0.4 requires phpstan/phpstan ^2.0.4 -> satisfiable by phpstan/phpstan[2.0.4, ..., 2.1.x-dev].
- rector/rector 2.0.5 requires phpstan/phpstan ^2.1.0 -> satisfiable by phpstan/phpstan[2.1.0, 2.1.1, 2.1.2, 2.1.x-dev].
- rector/rector[2.0.6, ..., 2.0.7] require phpstan/phpstan ^2.1.1 -> satisfiable by phpstan/phpstan[2.1.1, 2.1.2, 2.1.x-dev].
- Conclusion: don't install phpstan/phpstan 2.1.2 (conflict analysis result)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request