My Jetpack: migrate interstitial Buttons to @wordpress/ui

[CGastrell]

Fixes #

Proposed changes

Follow-up to #48414. Migrates the Button imports in the My Jetpack interstitials away from @automattic/jetpack-components and @wordpress/components to the new Button from @wordpress/ui, in line with the broader Jetpack UI Modernization effort.

NOTE: disregard the Dolly quotes overlapping with action buttons, that is being worked on #48472

Files touched

• pricing-interstitial.jsx — free / paid / bundle tier CTAs and the actions-slot "Use license key" button.
• product-interstitial.jsx — actions-slot "Use license key" button.
• jetpack-ai/more-requests.jsx — "Contact Us" + "Back" buttons.

Prop migration

Old (@automattic/jetpack-components / @wordpress/components)	New (@wordpress/ui)
variant="primary" (default)	variant="solid" (default)
variant="secondary"	variant="outline"
isLoading={ … }	loading={ … }
fullWidth	small tier-cta width:100% class
href={ url }	render={ <a href={ url } /> } + nativeButton={ false }
<Link to="..."><Button/></Link> (invalid HTML)	<Button render={ <Link to="..." /> } />

CSS layer workaround

@wordpress/ui Button styles live inside @layer wp-ui-components. wp-admin ships an un-layered a { color: var(--wp-admin-theme-color) } rule which wins over the layered button rule (un-layered styles always beat layered ones), so any Button rendered as an anchor (via render={<a/>} or render={<Link/>}) ends up with admin link blue text instead of the button's intended foreground colour — solid-variant buttons in particular render with invisible text (blue on blue).

This PR adds a single non-layered rule in _inc/style.module.scss that re-asserts --wp-ui-button-foreground-color on anchor-rendered @wordpress/ui Buttons, scoped to body.jetpack_page_my-jetpack.

Drive-bys

• The "Back" button in more-requests.jsx previously rendered as <a><button/></a> (invalid HTML). Moving react-router's <Link> into the Button's render prop produces a single, valid <a> element.

Related product discussion/links

• #48414 — interstitials unified header (PR being followed up)
• #48160 — Jetpack UI Modernization tracking issue

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

No. All onClick analytics handlers (jetpack_myjetpack_interstitial_license_link_click, jetpack_myjetpack_product_interstitial_back_link_click, jetpack_ai_upgrade_contact_us) are preserved.

Testing instructions

1. Visit each /wp-admin/admin.php?page=my-jetpack#/add-* route on a Jetpack-connected site (e.g. /add-akismet, /add-security, /add-jetpack-ai).
2. Confirm the "Use license key" action button in the page header renders as a compact outlined button and navigates to #/add-license.
3. On a tiered-pricing page (e.g. /add-akismet, /add-jetpack-ai), confirm the Free / Paid / Bundle tier CTAs render full-width with the right primary/outline treatment.
4. Click any tier CTA; confirm only the clicked button shows the loading spinner while all three buttons disable until the action settles.
5. Force-render the Jetpack AI "more requests" interstitial (it's reached when the AI request quota is exhausted). Confirm the "Contact Us" button is solid-blue with white text (the layer override is what makes that work) and that "Back" is outlined.
6. Mobile / narrow viewport: header reflows, tier CTAs stack appropriately.

Changelog

• packages/my-jetpack — patch / changed entry covers the Button migration.

[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 feat/mj-interstitial-buttons-wp-ui branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack feat/mj-interstitial-buttons-wp-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!

[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

_{Coverage check overridden by Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR .}