-
Notifications
You must be signed in to change notification settings - Fork 798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
General: update our PHP version requirements to PHP 7.0 #34126
Conversation
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped. Beta plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Jetpack plugin: The Jetpack plugin has different release cadences depending on the platform:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Debug Helper plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Backup plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Vaultpress plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Boost plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Search plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Social plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Starter Plugin plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Protect plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Videopress plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Super Cache plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Migration plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Mu Wpcom plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Inspect plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
Co-authored-by: Brad Jorsch <[email protected]>
projects/plugins/debug-helper/changelog/update-php-requirements
Outdated
Show resolved
Hide resolved
projects/plugins/mu-wpcom-plugin/changelog/update-php-requirements
Outdated
Show resolved
Hide resolved
This should be updated too
|
projects/packages/codesniffer/tests/php/tests/files/i18n-text_domain-not-set.php.ruleset.xml
Outdated
Show resolved
Hide resolved
…domain-not-set.php.ruleset.xml Co-authored-by: Brad Jorsch <[email protected]>
Co-authored-by: Brad Jorsch <[email protected]>
Co-authored-by: Brad Jorsch <[email protected]>
See: - #34126 (comment) - #34126 (comment) - #34126 (comment) - #34126 (comment) Co-authored-by: anomiex <[email protected]>
I'd rather not do that here, to be honest. The VaultPress plugin still requires WordPress 5.2:
I'm thinking we should update that before we up the PHP requirement. I do not recall why we haven't updated the WordPress requirement in the past, but I assume there is a reason. We last updated it before we brought it to the monorepo, in Automattic/vaultpress#101 I couldn't find anything on p2 either. Maybe worth doing in a follow-up PR? |
These should match. If you'd rather leave them both at 5.6 for now, I could go with that.
|
Ah yeah, I didn't mean to replace that one, thank you! 82cbf50 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is no longer happening, delete this file. Then the plugin's version will need to be un-bumped too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's do it!
This makes for a better experience for third parties using the packages, as they can see on Packagist which PHP versions the package is supposed to support. Also this is a good excuse to make a major version bump for all the packages following #34126 which removed testing with PHP 5.6 and allows use of 7.0+ features going forward. And since we're making systematic use of declared PHP versions now, let's lint for that and make use of it to skip phpunit tests where appropriate.
This makes for a better experience for third parties using the packages, as they can see on Packagist which PHP versions the package is supposed to support. Also this is a good excuse to make a major version bump for all the packages following #34126 which removed testing with PHP 5.6 and allows use of 7.0+ features going forward. And since we're making systematic use of declared PHP versions now, let's lint for that and make use of it to skip phpunit tests where appropriate.
Fixes #31714
Proposed changes:
Now that WordPress 6.4 is available, our plugins will be able to drop support for WordPress 6.2 and require WordPress 6.3 (to happen in a follow-up PR, #34127).
WordPress 6.3 introduced a new PHP version requirement: PHP 7.0. We can now match that requirement in all our tools.
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions: