Feature Request
I think we need a branch that cherry-picked from 0.16.0 tag. The reason is sometime, PHPStan has new config and it just break the existing 0.* tag, and there is now way to resolve it except use previous PHPStan version, or bump to use dev-main of rector, while that certainly break consumer extensions per current code changes go to v1.
My idea is to :
- create a branch named 0.16.x in rector-src pulled from latest 0.16.0 tag, which can have separate prefix build script to build into rector/rector repository with same branch name.
- When new phpstan config added that broke 0.16 version, we can create new relaease base of that branch.
This also can have time for user to prepare to migrate to v1 when v1 ready.
Feature Request
I think we need a branch that cherry-picked from 0.16.0 tag. The reason is sometime, PHPStan has new config and it just break the existing 0.* tag, and there is now way to resolve it except use previous PHPStan version, or bump to use
dev-mainof rector, while that certainly break consumer extensions per current code changes go to v1.My idea is to :
This also can have time for user to prepare to migrate to v1 when v1 ready.