Key details

  1. Polaris Web Components 2.0 stable release: October 22, 2026.
  2. polaris-2.js tracks latest 2.x; polaris-2.0.js pins the 2.0 release.
  3. polaris.js and polaris-1.js remain on 1.1; no automatic 2.x migration.
  4. React Router template requires matching polarisUrl settings and @shopify/shopify-app-react-router 2.1.0 or later.
  5. TypeScript projects should use @shopify/polaris-types 2.x.
  6. Built for Shopify embedded App Home design-alignment deadline: May 1, 2027.
  7. Admin UI and App Home UI extensions update visual treatment automatically; embedded App Home interfaces differ.
  8. Shopify has not set an October 2026 forced retirement date for Polaris 1.x.

What builders should take away

  1. Audit which Polaris CDN script each embedded app loads before planning an upgrade.
  2. Test both old and redesigned Shopify admin appearances, including save bars, side panels, long forms, errors and fixed-position elements.
  3. If using the React Router template, update client and server Polaris URLs together and verify the package version.
  4. For a heavily customised app or older Polaris React interface, budget for CSS and component migration rather than assuming a one-line CDN change.
  5. Do not confuse the May 2027 Built for Shopify visual requirement with a general forced shutdown of Polaris 1.x.

What changed

On October 22, 2026, Shopify made Polaris Web Components 2.0 available on stable CDN channels as the first major release under its semantic versioning scheme. The new components can match the redesigned Shopify admin as it rolls out to merchants, while retaining the older visual treatment where that admin is still in use. Crucially, existing polaris.js and polaris-1.js script tags continue serving 1.1 and never automatically move to 2.x. Apps must opt in by loading polaris-2.js for the latest 2.x or polaris-2.0.js to pin the initial release. Shopify's September developer guidance separately gives Built for Shopify embedded App Home interfaces until May 1, 2027 to match the new admin visual style.

Why it matters

App developers now have a production-stable migration target rather than a release candidate, but the redesigned merchant admin can expose a mismatch with unchanged embedded app interfaces. Small teams maintaining older custom apps must identify which Polaris generation they use, choose whether to migrate, and test both admin appearances without accidentally loading duplicate bundles. Shopify says existing apps will not break simply because they remain on 1.x; this is an opt-in UI migration, not an immediate forced cutover. Built for Shopify status introduces a distinct future design-alignment deadline.

Stable CDN URLs preserve explicit major-version control

Shopify serves the latest 2.x release from polaris-2.js and offers polaris-2.0.js for teams that want to pin 2.0 specifically. The original polaris.js and polaris-1.js continue to serve 1.1. That protects existing interfaces from an automatic major-version change but means teams must deliberately adopt 2.x. The release is about embedded App Home web components, not a universal automatic restyle for every Shopify app.

React Router and TypeScript apps need coordinated configuration

For apps built from Shopify's React Router template, Shopify requires polarisUrl in both AppProvider and shopifyApp server configuration, with matching values, and @shopify/shopify-app-react-router 2.1.0 or later. TypeScript projects should use @shopify/polaris-types 2.x. Developers should ensure only one Polaris bundle loads, inspect custom CSS and legacy Polaris React components, and test overlays, save bars, side panels and sticky controls.

Two admin designs complicate migration testing

Shopify's redesigned admin began a progressive merchant rollout on September 15. Polaris 2.x chooses the appearance appropriate to the store's current admin. Shopify recommends testing a development store with the new-admin feature preview alongside the previous design. Developer forum reports during the release-candidate period described save-bar stacking and chip styling problems; these are anecdotal migration signals, not evidence that all remain unresolved in stable 2.0.

Deadlines differ by app programme and component type

Shopify says Built for Shopify embedded App Home interfaces should match the redesigned admin by May 1, 2027. It has not announced an end-of-support date for the 1.x CDN line in the October 22 release. Admin UI and App Home UI extensions receive the admin's design automatically and do not need this CDN opt-in; embedded apps using the older Polaris React component library require a more substantial move to web components.

What to watch next

  • Stable 2.x bug-fix releases and reports on save-bar or overlay compatibility.
  • Shopify's rollout progress for the redesigned merchant admin.
  • Any announced Polaris 1.x support or deprecation timeline.
  • Updated Built for Shopify visual-compliance guidance before May 1, 2027.

Still unclear

  • Shopify has not stated when, if ever, the legacy Polaris 1.x CDN will be retired.
  • Forum migration reports came from the release-candidate period and may have been fixed in the stable build.
  • App migration effort depends heavily on legacy React components and custom CSS.
  • The Built for Shopify visual deadline is programme-specific rather than a blanket deadline for all apps.

Sources

Direct reading behind this dossier.

4 sources
Polaris 2.0 is now stable
Shopify Developer Changelog primary

Stable release, CDN version behaviour and React Router/TypeScript requirements.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment