as I am again dealing with BC breaks in patch releases and broken build pipelines, just wanted to give you the feedback that renaming/moving of rector rules in patch/minor releases is a real pain for your users.
since it happens so frequently updating rector is a very frustrating experience. especially in repositories which can't have a composer.lock file (lib repos) and therefore need fixed version constraints, which then even impacts updates of other libraries.
even if we use the "sets" or similar pre-packaged rector configs we have to deal with these BC breaks, because the skip-rules work on a class-string basis
as I am again dealing with BC breaks in patch releases and broken build pipelines, just wanted to give you the feedback that renaming/moving of rector rules in patch/minor releases is a real pain for your users.
since it happens so frequently updating rector is a very frustrating experience. especially in repositories which can't have a composer.lock file (lib repos) and therefore need fixed version constraints, which then even impacts updates of other libraries.
even if we use the "sets" or similar pre-packaged rector configs we have to deal with these BC breaks, because the skip-rules work on a class-string basis