VideoPress: surface the admin dashboard in the Jetpack plugin

[vianasw]

Proposed changes

The Jetpack > VideoPress admin dashboard has, until now, only ever appeared in the standalone Jetpack VideoPress plugin — even though the dashboard itself lives entirely in the automattic/jetpack-videopress package that the Jetpack plugin already bundles.

The reason is a single init option. The package's Admin_UI::init() only runs when Initializer::should_initialize_admin_ui() is true, which is only the case when a consumer passes admin_ui => true to $config->ensure( 'videopress', … ). The standalone plugin does that; Jetpack::configure() lumped 'videopress' into a bare loop that called $config->ensure( $feature ) with no options, so the flag was never set and the menu never registered.

This PR pulls 'videopress' out of that no-options loop and ensures it with array( 'admin_ui' => true ), mirroring the standalone plugin.

• projects/plugins/jetpack/class.jetpack.php: ensure the videopress feature with admin_ui => true.

Behavior is unchanged unless the VideoPress module is active:

• The page is still gated by Status::is_active(), which inside the Jetpack plugin means the VideoPress module must be active (Jetpack, unlike the standalone plugin, does not force-activate the module).
• The existing rsm_jetpack_ui_modernization_videopress filter continues to select the UI: off → legacy React app, on → modernized wp-build dashboard. No new enablement mechanism is introduced.

All required assets (the legacy build/admin bundle and the full modernized build/ wp-build tree) and the jetpack-wp-build-polyfills dependency already ship in the Jetpack plugin's jetpack_vendor/ mirror, so no build changes are needed.

Related product discussion/links

• VIDP-251 (modernized VideoPress dashboard) — this PR makes that dashboard reachable from the Jetpack plugin, not just the standalone plugin.

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

No. No new tracking is introduced. The package's existing Tracks usage is unchanged and still gated by the standard analytics/consent checks.

Testing instructions

Prerequisite: a site with the Jetpack plugin only (the standalone Jetpack VideoPress plugin deactivated), and the VideoPress module active (wp jetpack module activate videopress).

1. Go to wp-admin → Jetpack. Confirm a VideoPress entry appears in the Jetpack submenu.
2. Visit admin.php?page=jetpack-videopress.
   • With rsm_jetpack_ui_modernization_videopress off (default), the legacy React app renders (mount node #jetpack-videopress-root, jetpack-videopress-pkg bundle).
   • With the filter on (e.g. add_filter( 'rsm_jetpack_ui_modernization_videopress', '__return_true' );), the modernized wp-build dashboard renders (mount node #jetpack-videopress-dashboard-wp-admin-app, @wordpress/boot script module).
3. With the VideoPress module inactive, confirm the page/menu does not appear (expected).

Verified locally in Docker with the standalone plugin deactivated: filter off → legacy app, filter on → modernized dashboard, both served by the Jetpack plugin alone.

🤖 Generated with Claude Code

[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), and enable the add/jetpack-videopress-admin-ui branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/jetpack-videopress-admin-ui

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 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: July 7, 2026
  • Code freeze: July 6, 2026

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

[jp-launch-control]

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