Skip to content

General: Update minimum WordPress version to 6.9#49021

Merged
tbradsha merged 3 commits into
trunkfrom
update/min-wp-to-6.9
May 28, 2026
Merged

General: Update minimum WordPress version to 6.9#49021
tbradsha merged 3 commits into
trunkfrom
update/min-wp-to-6.9

Conversation

@anomiex
Copy link
Copy Markdown
Contributor

@anomiex anomiex commented May 20, 2026 •
edited
Loading

Proposed changes

This updates the minimum WordPress version for our plugins (other than CRM and VaultPress) to 6.9, as we support only the current and previous versions. This is considered a "major change".

This also cleans up various obsolete Phan suppressions, a few tests, and some Phan config that was getting confused by recent additions of wp-build.

See #46801 for the previous bump, for comparison.

Related product discussion/links

None, apparently. 🙁

Does this pull request change what data or activity we track or use?

No

Testing instructions

  • Proofread.

@anomiex
General: Update minimum WordPress version to 6.9
1f70831 
This updates the minimum WordPress version for our plugins (other than
CRM, Premium Analytics, and VaultPress) to 6.9, as we support only the
current and previous versions. This is considered a "major change".

This also cleans up various obsolete Phan suppressions, a few tests, and
some Phan config that was getting confused by recent additions of
`wp-build`.

See #46801 for the previous bump, for comparison.
@anomiex anomiex self-assigned this May 20, 2026
@anomiex anomiex added the [Status] Needs Review This PR is ready for review. label May 20, 2026
@anomiex anomiex requested review from a team as code owners May 20, 2026 20:47
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 20, 2026 •
edited
Loading

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the update/min-wp-to-6.9 branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack update/min-wp-to-6.9

bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/min-wp-to-6.9

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@github-actions github-actions Bot added [Plugin] Inspect [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Plugin] Paypal Payment Buttons [Plugin] Protect A plugin with features to protect a site: brute force protection, security scanning, and a WAF. [Plugin] Search A plugin to add an instant search modal to your site to help visitors find content faster. [Plugin] Social Issues about the Jetpack Social plugin [Plugin] Starter Plugin [Plugin] VideoPress A standalone plugin to add high-quality VideoPress videos to your site. [Plugin] Wpcloud Sso [Plugin] Wpcomsh [Tests] Includes Tests [Tools] Development CLI The tools/cli to assist during JP development. Docs labels May 20, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 20, 2026 •
edited
Loading

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

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 🤖

Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

  • WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
  • WoA releases happen weekly.
  • Releases to self-hosted sites happen monthly:
    • Scheduled release: June 2, 2026
    • Code freeze: June 1, 2026

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Backup plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Boost plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Search plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Social plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Starter Plugin plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Protect plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Videopress plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Inspect plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Wpcomsh plugin:

  • Next scheduled release: Atomic deploys happen twice daily on weekdays (p9o2xV-2EN-p2)

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Automattic For agencies client plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Classic Theme helper plugin plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Paypal Payment buttons plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Wpcloud Sso plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Premium Analytics plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

@jp-launch-control
Copy link
Copy Markdown

jp-launch-control Bot commented May 20, 2026 •
edited
Loading

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

tbradsha
tbradsha reviewed May 21, 2026
View reviewed changes
Comment thread projects/packages/backup/.phan/config.php
array(
'+stubs' => array( 'woocommerce-internal' ),
'exclude_file_regex' => array(
'build/',
Copy link
Copy Markdown
Contributor

@tbradsha tbradsha May 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I had this on my list to update four projects.

Copy link
Copy Markdown
Contributor

@tbradsha tbradsha May 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like five now with premium-analytics. But you got them. 🎉

tbradsha
tbradsha previously approved these changes May 21, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@tbradsha tbradsha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Two questions, but no blockers.

  1. Why not bump the premium-analytics plugin?
  2. We could perhaps remove this comment:

    jetpack/projects/packages/search/src/search-blocks/class-search-blocks.php

    Lines 841 to 843 in 1f70831

    * Uses `register_block_template()` (WP 6.7+). Jetpack requires WP 6.8+,
    * so the function is always present at runtime — the function_exists
    * guard is defensive for phpstan/phan and edge environments.

As for that second point, I'm curious what the policy is for package support on old versions. For example, if one removed the guard in the latest version of the package, and I have an old WP and old Jetpack Search plugin, would things then break when latest Jetpack is installed (perhaps manually because WP.org would restrict it) because the autoloader would select the newest version of the package?

@anomiex
Copy link
Copy Markdown
Contributor Author

anomiex commented May 21, 2026 •
edited
Loading

  1. Why not bump the premium-analytics plugin?

It's currently on 6.6 rather than 6.8 (and its "tested up to" is only 6.8). We should figure out who owns that and see what they want to do. Which should probably be a separate PR anyway, if only to bring it into line with the rest of the monorepo going forward.

  1. We could perhaps remove this comment:

    jetpack/projects/packages/search/src/search-blocks/class-search-blocks.php

    Lines 841 to 843 in 1f70831

    * Uses `register_block_template()` (WP 6.7+). Jetpack requires WP 6.8+,
    * so the function is always present at runtime — the function_exists
    * guard is defensive for phpstan/phan and edge environments.

🤷.

As for that second point, I'm curious what the policy is for package support on old versions. For example, if one removed the guard in the latest version of the package, and I have an old WP and old Jetpack Search plugin, would things then break when latest Jetpack is installed (perhaps manually because WP.org would restrict it) because the autoloader would select the newest version of the package?

I can't say I'm too worried about that scenario, since they're already breaking their site by installing the newer Jetpack.

I don't know of any official written-down policy, generally I just assume "one previous" like for the plugins since that's all we actually test against.

@anomiex
Copy link
Copy Markdown
Contributor Author

anomiex commented May 21, 2026

We should figure out who owns that and see what they want to do.

Looking back at #48087, which was the only PR touching it, I think the answer is "no one cares, this exists only for testing in the first place". Given that, I'll go ahead and bump it too.

tbradsha
tbradsha approved these changes May 28, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@tbradsha tbradsha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@tbradsha tbradsha merged commit fff3820 into trunk May 28, 2026
205 of 224 checks passed
@tbradsha tbradsha deleted the update/min-wp-to-6.9 branch May 28, 2026 04:36
@github-actions github-actions Bot removed the [Status] Needs Review This PR is ready for review. label May 28, 2026
@kangzj kangzj mentioned this pull request May 28, 2026
Merged
8 tasks
@anomiex anomiex mentioned this pull request Jun 2, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@tbradsha tbradsha tbradsha approved these changes

Assignees

@anomiex anomiex

Labels

Docs [Feature] Contact Form [Feature] Related Posts [Feature] Subscriptions All subscription-related things such as paid and unpaid, user management, and newsletter settings. [Feature] Theme Tools [Package] Backup [Package] Classic Theme Helper [Package] Codesniffer [Package] Forms [Package] Import [Package] Newsletter [Package] Podcast [Package] Premium Analytics [Package] Scan [Package] Search Contains core Search functionality for Jetpack and Search plugins [Package] Stats Data [Package] Sync [Package] Wp Abilities [Package] Wp Build Polyfills [Plugin] Automattic For Agencies Client [Plugin] Backup A plugin that allows users to save every change and get back online quickly with one-click restores. [Plugin] Boost A feature to speed up the site and improve performance. [Plugin] Classic Theme Helper Plugin [Plugin] CRM Issues about the Jetpack CRM plugin [Plugin] Inspect [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Plugin] Paypal Payment Buttons [Plugin] Premium Analytics [Plugin] Protect A plugin with features to protect a site: brute force protection, security scanning, and a WAF. [Plugin] Search A plugin to add an instant search modal to your site to help visitors find content faster. [Plugin] Social Issues about the Jetpack Social plugin [Plugin] Starter Plugin [Plugin] VideoPress A standalone plugin to add high-quality VideoPress videos to your site. [Plugin] Wpcloud Sso [Plugin] Wpcomsh [Pri] Normal [Tests] Includes Tests [Tools] Development CLI The tools/cli to assist during JP development.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@anomiex @tbradsha