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) : [test] Test pin PHPStan 2.1.34 (working) rector-downgrade-php#359
• 2.1.35 (not working): [test] Test bump PHPStan 2.1.35 (not working) rector-downgrade-php#360
• Bump to PHPStan ^2.1.35 rector-src#7847
• PHPStan 2.1.35 cause error on rector-downgrade-php phpstan/phpstan#13992

The failing test case already reported to phpstan :)

• [PHPStan 2.1.35] Add failing test where original Node not processed under VirtualNode on NodeScopeResolver::processNodes() phpstan/phpstan-src#4795

Temporary solution is pin rector/rector to 2.3.2 and phpstan/phpstan to 2.1.34 for now :)

"rector/rector": "2.3.2",
"phpstan/phpstan": "2.1.34",