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 WordPress.com Simple 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, and enable the fix/submenu-jetpack-null branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack fix/submenu-jetpack-null
  

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin fix/submenu-jetpack-null
  

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

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 Team 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 🤖

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.

🔴 Action required: Please add missing changelog entries for the following projects: projects/packages/masterbar

Use the Jetpack CLI tool to generate changelog entries by running the following command: jetpack changelog add.
Guidelines: /docs/writing-a-good-changelog-entry.md

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

cc @vykes-mac since you're most likely familiar with the changes. Let me know if you have any thoughts or feedback.

cc @vykes-mac since you're most likely familiar with the changes. Let me know if you have any thoughts or feedback.

@ecairol Thanks for the ping. Based on the described issue this guard check looks reasonable.

@vykes-mac - Hello! We have a team51 partner who is waiting on this fix. Just so we know how to proceed with that particular site - would this patch just be added to the next release, or would it be sooner? I know it is an edge case (so not an urgent issue), but we want to know whether we should just patch it locally on this particular site until the next release. Thank you!

@vykes-mac - Hello! We have a team51 partner who is waiting on this fix. Just so we know how to proceed with that particular site - would this patch just be added to the next release, or would it be sooner? I know it is an edge case (so not an urgent issue), but we want to know whether we should just patch it locally on this particular site until the next release. Thank you!

I think it's okay to apply the patch on your end while waiting for the next jetpack release.