Roadmap for 4.x

Problem/Motivation

We have a 4.x branch which diverges a bit from 3.x, and I'd like to close 3.x fairly soon, as managing two branches is a pain, especially when cherry-picks will tend to conflict.

From Slack conversation:

Grimreaper
Branch 4 main breaking change was potentially ability to handle user content entities. And a breaking change in remote website settings (I don't remember exactly which one and even if it had been merged or not).
If you want to make it stable without users handling, etc. Go for it
Also with PHPStan level max potentially other breaking changes

joachim
Ok, will do. We can prob add user handling as a minor update — if it’s not enabled by default in existing sites

My rough plan is:

1. Fix broken tests on 4!
2. 🐛 Editing a path alias on the server to point elsewhere causes a broken state with aliases on the client on pull Active , as that is going to change path_alias behaviour, so safer to say it's a 4.x thing
3. 📌 ImportService shouldn't hold stateful data in the RuntimeImportContext Active