Just preparing notes for next release... ...Rector got 25-30 % faster since the last one 🚀🚀🚀 (one more performance feature left to go...) Stay tuned

We've launched a brand new website design couple weeks ago, with focus on clear docs, advanced rule filters and beautiful code snippets 🤩 How do you like it? (Press "F" or "D" for easter 🥚)

Next Rector release will not blindly run all the Symfony rules, that were useful historically. Instead, most of rule will be capped by composer version they run on, making Rector run faster and more focused on your current version 👌 Discover more about composer-based sets 👇 getrector.com/documentation/…

"Should we rewrite or upgrade?" That question costs teams years when it's answered by guessing. We've reviewed hundreds of PHP codebases. We'll tell you which one your app actually needs - and in what order - in 2 weeks. getrector.com/codebase-audit

Simpler, clearer, focused on upgrades and delivery. New getrector.com/ website is here 🥳🥳🥳

We're cooking something...

Sometimes you don't want to run all the rules, but not just 1 either. Sometimes you want to run 3-5 rules that handle some logical group, like return type declarations. In the next Rector release, you can We added support to run multiple rules via --only 🎉

Composer-based sets for Symfony and PHPUnit now first class citizens in @rectorphp 2.6 😍

Did you know you can run just single rule on the whole codebase? Keeps your diff simple and easy to merge Just use --only=YourCustomerRector ⭐ since Rector 2.6 with broader values

It's the little details that devs appreciate... Part of code quality set 😇