Compatibility: Removing import fallbacks as we no longer need to ensure compatiblity

[coder-karen]

Fixes VULCAN-201

Proposed changes:

• This PR removes the fallbacks that were added over three different PRs, to ensure compatibility with older versions of Gutenberg. These are no longer needed as we expect minimum versions of WordPress used to be 6.6, and P2 (which was the issue), has now had it's version of Gutenberg updated.
• The three PRs involved, were Jetpack SEO: Ensure more performant practices when getting enabled features. #43109, Compatibility: move from Post Editor to Site Editor versions of Utilities #42652 and Social: Fix deprecation warnings for WP 6.6 #42634

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

n/a

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

No.

Testing instructions:

A code review should be sufficient, and then primarily testing on P2 as that was why compatibility was added:

• Sandbox a P2 site, and apply these changes using the command in the generated comment below in your sandbox.
• Visit the P2, and open up WP Admin in order to create a new post. In the post editor, attempt to add core blocks such as the checkbox block, task block. Also the gif block. These should work, as should auto-complete when using @ and +.
• You can also test with comments on the P2 front-end (for example with @ and + autocomplete, and adding the task block and gif block - in order to replicate similar testing scenarios as were used when the issue from the earlier PR was present, you should also try adding ?concat=yes to the URL.
• Open up the Jetpack sidebar after creating a new post in WP Admin. Ensure there are no warnings showing on the page.

However, to fully test all areas of code touched, then follow the testing steps in these PRs:

• Social: Fix deprecation warnings for WP 6.6 #42634
• Compatibility: move from Post Editor to Site Editor versions of Utilities #42652
• Jetpack SEO: Ensure more performant practices when getting enabled features. #43109

(note that you shouldn't be seeing console warnings at any stage of testing)

Some additional notes:

• Rather than testing console warnings, more importantly test that functionality remains as expected.
• For SEO testing, on self-hosted you'll need a Complete plan. Also, you may not see the auto-generated title etc in the Jetpack sidebar, but it should show in the pre-publish panel.
• For the Compatibility (Post Editor to Site Editor) PR, The AI Assistant and Yoast Promo steps aren't relevant for SImple, nor the Payments Post Publish Panel
• The Social PR steps can only be tested on self-hosted

[github-actions]

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/gutenberg-wordpress-compatibility-conditionals branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/gutenberg-wordpress-compatibility-conditionals

bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/gutenberg-wordpress-compatibility-conditionals

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]

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 a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ 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: August 5, 2025
  • Code freeze: August 4, 2025

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

[jp-launch-control]

Code Coverage Summary

Coverage changed in 13 files. Only the first 5 are listed here.

File	Coverage	Δ%	Δ Uncovered
projects/js-packages/publicize-components/src/components/block-editor/components/pre-publish-panels.tsx	0/5 (0.00%)	0.00%	-1 💚
projects/js-packages/publicize-components/src/components/post-publish-manual-sharing/index.tsx	0/5 (0.00%)	0.00%	-1 💚
projects/js-packages/publicize-components/src/components/post-publish-review-prompt/index.tsx	0/15 (0.00%)	0.00%	-1 💚
projects/js-packages/publicize-components/src/components/post-publish-share-status/index.tsx	0/17 (0.00%)	0.00%	-1 💚
projects/plugins/jetpack/extensions/blocks/premium-content/_inc/remove-block-keep-content.js	0/3 (0.00%)	0.00%	-1 💚

Full summary · PHP report · JS report

[bindlegirl]

Tested. LGTM