Release v2.7.0

[snim2]

This is a breaking change which removes support for versions of PHP less than 8.

Resolves: https://...

• Includes tests (if new features are introduced)
• Commit message includes link to the ticket/issue
• Changelog updated
• [-] PR open against dxw's Homebrew Tap to point the Whippet formula to the new version number

[RobjS]

I think the theoretical view of PHP version bumps is that they aren't breaking changes, see e.g. https://www.doctrine-project.org/2017/07/25/php-7.1-requirement-and-composer.html#why-dropping-php-support-in-a-minor-version-is-not-a-bc-break

But I've also seen people complain when PHP bumps have been treated like that, and it did end up breaking things.

I'm of two minds here; my general preference would be to be on the safe side and make it a major version bump. However, every single project we have references Whippet v2 in its root composer.json (and uses that Composer file to install Whippet in CI), so we'll have to bump each of those individually if we make this a major version release.

[snim2]

I think the theoretical view of PHP version bumps is that they aren't breaking changes, see e.g. https://www.doctrine-project.org/2017/07/25/php-7.1-requirement-and-composer.html#why-dropping-php-support-in-a-minor-version-is-not-a-bc-break

But I've also seen people complain when PHP bumps have been treated like that, and it did end up breaking things.

I'm of two minds here; my general preference would be to be on the safe side and make it a major version bump. However, every single project we have references Whippet v2 in its root composer.json (and uses that Composer file to install Whippet in CI), so we'll have to bump each of those individually if we make this a major version release.

That's a good point. OK, I'll force-push a minor version release.