-
Notifications
You must be signed in to change notification settings - Fork 148
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
[TASK] Upgrade to PHPStan 2.x and Rector 2.x #777
Conversation
For this change, we'll need to drop support for PHP < 7.4 first. |
PHP 7.4 just becomes a dev requirement, not a minimum requirement for the package. Ideally we can find a way of running the versions of the tools compatible with the version contraints. Oh, Composer. It's what it's there for. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An OR-list for the versions in composer.json
would solve the dependency hell issue. It's what it's there for. There's no reason to drop support for PHP<7.4.
composer.json
Outdated
"phpstan/phpstan": "2.0.3", | ||
"phpstan/phpstan-phpunit": "2.0.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need an OR-list of versions, e.g. "phpstan/phpstan": ".12.0 || 2.0.3"
. That way we can have the new version installed when the PHP environment allows, whilst also continuing to support older PHP versions.
01c6f86
to
d10a5ca
Compare
Also add some more return type declarations as added by the new Rector version.
d10a5ca
to
3580e45
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WFM. We can deal with the PHPStan-reported issues at a later stage.
- dependency-name: "phpunit/phpunit" | ||
versions: [ ">= 9.0.0" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we probably don't want the bot to try a major update of PHPUnit, which would be incompatible.
I removed the non-applicable commit message that was separately done with #778. |
No description provided.