Outside the recent fun from our Terminator

We must understand semantic versioning differently because a minor change such as 3.1 to 3.2 indicates there is no backward compatibility break.

While I agree that nobody is interested in CI 3 with a BC break, that might not be possible in consideration of which versions of PHP are actively supported. It seems a disservice to the world's developers to supply a framework with a backbone (PHP) using obsolete and vulnerable code. But making PHP v7.3 or greater a requirement would almost certainly break something for many (most?) existing CI v3 based apps.