Version Packages (canary)

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to canary, this PR will be updated.

Releases

@bigcommerce/catalyst@1.3.0

Minor Changes

• #3156 9990a87 Thanks @jordanarldt! - Print the DNS records to publish when catalyst domains add succeeds. The A and CNAME values that point the domain at the project are shown with the success message, along with which to publish and a note that they are only returned when the domain is added. The records survive --wait, and are omitted when the API has none to share yet.

• #3166 382bdf5 Thanks @jordanarldt! - Standardize resource commands on plural names: catalyst project is now catalyst projects, and catalyst channel is now catalyst channels, matching the already-plural domains and logs. The singular form of every resource command remains as an alias — project, channel, domain, and log all still resolve — so existing scripts keep working. Telemetry continues to report the canonical plural name regardless of which form was typed.

Patch Changes

• #3164 eef0c18 Thanks @jordanarldt! - Stop asking users to log in again after catalyst create. Credentials from the initial authentication are now written to the new project's .bigcommerce/project.json on every scaffold, not just --hosting commerce, so catalyst deploy no longer fails with "Missing credentials" and catalyst project create no longer re-prompts for login.

• #3167 2ec54df Thanks @jordanarldt! - Print every request under catalyst logs tail --format request, including requests that emitted no log messages. Previously each line was tied to a log entry, so a request that logged nothing disappeared from the stream. The request format now reads [timestamp] METHOD URL (status) [LEVEL] message, moving the level after the request details in both logs tail and logs query. catalyst logs tail --help now documents each format and notes that default and short only show requests with a message body.

• #3178 a78f93c Thanks @jorgemoya! - Stop catalyst deploy from wiping stored deployment environment variables. Commerce Hosting setup rebuilt .bigcommerce/project.json from scratch, dropping anything it didn't write itself — the env block managed by catalyst env, the persisted apiHost, and stored credentials when setup ran without them. Because deploy re-runs setup whenever the project isn't fully transformed, a routine deploy could silently discard variables that are sent as secrets on every deploy, leaving the next one to ship without them. Setup now merges into the existing file.

@bigcommerce/catalyst-client@1.0.3

Patch Changes

• #3158 be1967c Thanks @jorgemoya! - Surface a clearer error when BIGCOMMERCE_STOREFRONT_TOKEN is not a storefront JWT. Previously an incompatible token (e.g. an OAuth access token) produced a bare 401 with no explanation. The client now detects when a 401 is returned with a token that isn't a well-formed storefront JWT and throws InvalidStorefrontTokenError explaining that a storefront JWT is required and how to generate one.

@bigcommerce/create-catalyst@2.0.4

Patch Changes

• Updated dependencies [9990a87, eef0c18, 382bdf5, 2ec54df, a78f93c]:
  • @bigcommerce/catalyst@1.3.0

@bigcommerce/catalyst-core@1.11.0

Minor Changes

• #3062 98b618f Thanks @bc-yaroslav-zhmutskyi! - Add Wallet Payment buttons integration for cart page

  What changed

  • Render wallet payment buttons (e.g. PayPal) on the cart page when payment wallets are configured for the cart.
  • Added getPaymentWallets, getPaymentWalletWithInitializationData, and getCurrencyData GraphQL queries in the cart's page-data.ts to fetch configured wallets and their initialization data.
  • Added a ClientWalletButtons client component (core/components/wallet-buttons) that streams wallet init options and renders a container per wallet button.
  • Added a WalletButtonsInitializer (core/lib/wallet-buttons) that lazily injects the BigCommerce Checkout SDK loader script and initializes each wallet button against the /graphql endpoint, with an InitializationError for missing loader.
  • Wired walletButtonsInitOptions and cartId through the cart section component, and exposed getCurrencyData currency formatting details.
  • Extended the GraphQL proxy (with-graphql-proxy.ts / proxy.ts) to support Checkout SDK wallet-button requests.
  • Added NEXT_PUBLIC_CHECKOUT_SDK_DEV_URL to .env.example to optionally override the Checkout SDK loader URL in development.
  • Added e2e coverage (wallet-buttons.spec.ts) verifying the loader script and wallet button containers render only when wallets are configured.

Patch Changes

• #3181 20b55e0 Thanks @animesh1987! - Display an error message and disable Add to Cart when the requested quantity exceeds available-to-sell (on-hand + backorder allowance) on the PDP.

• #3181 20b55e0 Thanks @animesh1987! - Only show the "ready to ship" quantity message in the cart when part of the line item is also backordered. Previously it appeared any time showQuantityOnHand was enabled and any quantity was on hand, even for fully in-stock items where the message added no useful information.

• #3173 06775b2 Thanks @jordanarldt! - Resolve merchant-configured locale subfolders at runtime instead of baking them in at build time, so custom locale paths such as /fr-fr and /es-es resolve consistently.

  Previously the subfolder table was captured during next build into build-config.json and statically imported by i18n/locales.ts. If the control panel returned incomplete locale data at build time, every localized URL 404'd until the next deploy — and because next-intl treats a custom subfolder as a replacement for the bare locale code rather than an alias, there was no fallback: /es-es simply did not match any route.

  What changed

  • Added i18n/locale-config.ts, which reads locale configuration from BigCommerce at runtime and caches it in KV with the same stale-while-revalidate pattern as proxies/with-routes.ts. An empty locale list is never cached.
  • Locales are no longer written to build-config.json at all. A build-time snapshot of merchant-configurable data is either redundant or wrong, and using it as a fallback risked silently serving the stale URL space this change exists to fix. Runtime is now the only source. A warm cache rides out a BigCommerce outage; only a cold cache combined with an unreachable API cannot resolve, and that returns 503 with retry-after rather than a 404 that would tell crawlers these pages are gone.
  • proxies/with-intl.ts now builds its next-intl middleware per request from that configuration. It resolves the configuration once per request and forwards it to the render as x-bc-locale-routing, so rendering and redirects reuse exactly what resolved the inbound URL rather than fetching it again — the two can't disagree, and there is no extra round trip. It also passes the matched subfolder as x-bc-locale-prefix, which proxies/with-routes.ts strips instead of recomputing from build-time data.
  • Link, useRouter and usePathname now read the runtime configuration through a new provider in app/[locale]/layout.tsx, so generated URLs agree with what the proxy resolves. Canonical and hreflang URLs in lib/seo/canonical.ts and the header locale switcher do the same.
  • redirect and permanentRedirect moved from ~/i18n/routing to ~/i18n/navigation-server and are now async — await them. This keeps the GraphQL client and KV out of the client bundle.
  • Removed generateStaticParams from app/[locale]/layout.tsx, which only added a build-time dependency on the locale list — every route under [locale] already renders on demand because the tree reads cookies. The build's route rendering modes are unchanged.
  • i18n/locales.ts is removed. The locale gates in i18n/request.ts and app/[locale]/layout.tsx now use the runtime list, and the sitemap/robots/favicon routes resolve the default channel directly instead of routing through a locale.

  Behaviour change for channel-per-locale stores: robots.txt, the sitemap index and the favicon now resolve the default channel directly rather than via the default locale, because they run outside the proxy and have no request locale. Stores that map their default locale to a non-default channel in channels.config.ts will see those three served from BIGCOMMERCE_CHANNEL_ID.

  Locale detection is unchanged: a shopper is still redirected to their language's subfolder, and an explicit choice in the locale switcher still wins on later requests.

  Fixed along the way:

  • /xmlsitemap.php and /admin redirected through the locale-aware helper, resolving to /<locale>/sitemap.xml and /<locale>/ whenever every locale carries a prefix. The sitemap target was a 404, since /sitemap.xml is excluded from the proxy. Both now use plain redirects; /admin also no longer performs an uncached GraphQL request on every hit to a route that is disabled by default.
  • Losing the KV cache no longer takes the storefront down. A read failure now degrades to a fetch instead of being treated as unresolvable.
  • Locale configuration is validated where it is fetched, so an unusable value can no longer be cached and then rejected on every read, which would have silently turned the cache into a per-request refetch. Subfolders are normalized (surrounding slashes and whitespace trimmed), and locale codes and prefixes are constrained to safe URL shapes.
  • An unrecognised locale returns 404 rather than 500 when no message file exists for it.
  • A locale whose configured subfolder cannot be expressed in a URL is now skipped individually, with an error logged, instead of making the whole configuration unusable.
  • The Playwright URL fixtures asserted /<locale-code>/... instead of the configured subfolder, so alternate-locale assertions were wrong for any store whose subfolder differs from its locale code (for example de served at /de-de). They now resolve the subfolder from the store.

• #3176 332aa76 Thanks @jorgemoya! - Expire entries in the in-memory KV layer after 60 seconds. lib/kv keeps a per-process MemoryKvAdapter in front of whichever shared adapter is selected (Cloudflare KV, Upstash, Vercel Runtime Cache) and skips the shared store whenever memory holds every requested key. Those entries never expired, so once a process had seen a key it stopped consulting the shared store for it entirely. Refreshes were then driven solely by the expiryTime each caller embeds in the cached value — and that path refetches from the origin, not from the shared store. So every process independently refetched on a clock starting from whenever it first cached the key, rather than picking up a value another process had already fetched and shared. Cached data was never wrong, but origin requests and cache writes scaled with process count. Capacity is also raised from 500 to 4096 entries, since cache keys include the query string and so accumulate faster than the number of real paths suggests.

• #3171 0c49112 Thanks @chanceaclark! - Fix session cookie deletion being silently broken after logout. stripSessionCookieExpiry was stripping Expires from all session token Set-Cookie headers, including deletion directives (empty value + Expires=past). This turned cookie deletions into permanent empty-value session cookies, so the browser never removed them and stale cookies accumulated across login/logout cycles.

• #3174 f647d91 Thanks @jordanarldt! - Fix the product page og:image tag pointing at an unfetchable URL. ProductPageMetadataQuery requested urlTemplate, which returns a URL containing a literal {:size} placeholder that the <Image> CDN loader substitutes at render time. generateMetadata has no such loader, so the placeholder was emitted verbatim into the Open Graph tag.

  Migration

  In core/app/[locale]/(default)/product/[slug]/page-data.ts, update the defaultImage selection in ProductPageMetadataQuery to request a concrete URL:

    defaultImage {
      altText
  -   url: urlTemplate(lossy: true)
  +   url(width: 1200, lossy: true)
    }

  width: 1200 matches the Open Graph and summary_large_image recommendation. Height is omitted intentionally — the stencil resizer fits the image inside the given box rather than cropping, so requesting 1200x630 would return a smaller square image for a square product photo.

• #3081 50a7263 Thanks @mfaris9! - Fix Account Registration validating State/Province as required for countries without any states (e.g., Algeria). The register page now queries per-country state data from BigCommerce and hides the State/Province field entirely when the selected country has no states.

• #3157 27eec2f Thanks @bc-svc-local! - Update translations.

• #3175 2fada34 Thanks @bc-svc-local! - Update translations.

• Updated dependencies [be1967c]:

  • @bigcommerce/catalyst-client@1.0.3

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
catalyst	Ready	Preview	Aug 19, 2026 4:16pm

[github-actions]

Unlighthouse Performance Comparison — Vercel

Comparing PR preview deployment Unlighthouse scores vs production Unlighthouse scores.

Summary Score

Aggregate score across all categories as reported by Unlighthouse.

	Prod Desktop	Prod Mobile	Preview Desktop	Preview Mobile
Score	90	92	91	95

Category Scores

Category	Prod Desktop	Prod Mobile	Preview Desktop	Preview Mobile
Performance	76	71	70	84
Accessibility	95	98	95	95
Best Practices	100	100	100	100
SEO	88	88	88	100

Core Web Vitals

Metric	Prod Desktop	Prod Mobile	Preview Desktop	Preview Mobile
LCP	3.7 s	5.4 s	5.9 s	4.6 s
CLS	0.04	0.184	0.037	0
FCP	1.2 s	1.2 s	1.2 s	1.2 s
TBT	0 ms	0 ms	0 ms	0 ms
Max Potential FID	50 ms	50 ms	50 ms	50 ms
Time to Interactive	3.7 s	5.4 s	5.9 s	4.6 s

Full Unlighthouse report →