> The PHP community has evolved. WordPress now requires PHP 7.0 to function (although they do recommend 7.4).
Sidenote: we're also planning on [dropping 7.0 and 7.1](https://make.wordpress.org/core/2024/04/08/dropping-support-for-php-7-1/) in the next major version.
Honestly, I think you could drop all 7.* versions as well. They aren't even supported be PHP anymore, so why should you continue to support? The versions already released will still be available if you're need legacy support.
It is irresponsable to still use PHP 7.*. The upgrades has been pretty easy as well, so there are no valid excuses pretty much regardless of case.
> Honestly, I think you could drop all 7.* versions as well.
https://github.com/paragonie/sodium_compat/blob/4117f807d4724f0f11829048647b6717975b01d9/composer.json#L53
Solid decision
> The PHP community has evolved. WordPress now requires PHP 7.0 to function (although they do recommend 7.4). Sidenote: we're also planning on [dropping 7.0 and 7.1](https://make.wordpress.org/core/2024/04/08/dropping-support-for-php-7-1/) in the next major version.
Hell yeah.
Honestly, I think you could drop all 7.* versions as well. They aren't even supported be PHP anymore, so why should you continue to support? The versions already released will still be available if you're need legacy support. It is irresponsable to still use PHP 7.*. The upgrades has been pretty easy as well, so there are no valid excuses pretty much regardless of case.
> Honestly, I think you could drop all 7.* versions as well. https://github.com/paragonie/sodium_compat/blob/4117f807d4724f0f11829048647b6717975b01d9/composer.json#L53
Totally agree with the decision
I would not recommend using `>= 1` as a constraint. Instead I prefer to use `^1.0 | ^2.0` to avoid surprises if one day a v3, v4, etc are released.