This to avoid user keep creating known issue after run composer update and got phpstan 2.1.35 The new PHPStan 2.1.35 cause new issue seems due to change behaviour of `PHPStan\Analyser\NodeScopeResolver`, see related PRs and issue: - 2.1.34 (working) : https://github.com/rectorphp/rector-downgrade-php/pull/359 - 2.1.35 (not working): https://github.com/rectorphp/rector-downgrade-php/pull/360 - https://github.com/rectorphp/rector-src/pull/7847 - https://github.com/phpstan/phpstan/issues/13992 The failing test case already reported to phpstan :) - https://github.com/phpstan/phpstan-src/pull/4795 Temporary solution is pin **rector/rector to 2.3.2** and **phpstan/phpstan to 2.1.34** for now :) ```suggestion "rector/rector": "2.3.2", "phpstan/phpstan": "2.1.34", ```
This to avoid user keep creating known issue after run composer update and got phpstan 2.1.35
The new PHPStan 2.1.35 cause new issue seems due to change behaviour of
PHPStan\Analyser\NodeScopeResolver, see related PRs and issue:The failing test case already reported to phpstan :)
Temporary solution is pin rector/rector to 2.3.2 and phpstan/phpstan to 2.1.34 for now :)