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-client@1.0.4

Patch Changes

• #3263 4db7221 Thanks @jorgemoya! - Retry Storefront GraphQL queries that fail on a dropped connection or a 502, 503, or 504. Previously a single upstream hiccup threw straight to the error page ("There was a server error!"). Queries are now retried up to twice, after 100ms and 300ms, including when the connection drops while the response body is being read (TypeError: terminated). Mutations are never retried, since they aren't idempotent, and 4xx responses, GraphQL errors, and aborted requests fail immediately as before. Each retry logs a console.warn naming the operation, the attempt, and the failure (for example [BigCommerce] Retrying query GetSite after HTTP 502 (attempt 2 of 3)), so recovered failures still show up in server logs.

@bigcommerce/catalyst-core@1.12.3

Patch Changes

• #3254 75aa709 Thanks @jorgemoya! - Fix the cart shipping estimator not updating until a page reload. After "View shipping options", "Add shipping", or a quantity change, the shipping form now reflects the new address, quote, and selected option immediately.

  Migration

  In core/vibes/soul/sections/cart/client.tsx, key the ShippingForm on the server's shipping state so it remounts when that state changes:

  {
    shipping && (
      <ShippingForm
        key={JSON.stringify([
          shipping.address,
          shipping.shippingOptions,
          shipping.shippingOption?.value,
          shipping.showShippingForm,
        ])}
        {...shipping}
      />
    );
  }

• #3261 24dacae Thanks @jorgemoya! - Speed up routing cache reads on BigCommerce Native Hosting. The Cloudflare KV adapter now caches reads at each Cloudflare location for 5 minutes instead of Workers KV's 60-second default, so most with-routes lookups that miss the in-process cache take a few milliseconds instead of a trip to central KV storage. The trade-off is staleness: in the worst case, a storefront status change (maintenance mode, launch) can take up to about 11 minutes to reach a location instead of about 7. It's usually sooner, since the background refresh's write is normally visible at once in the location that made it. Route changes have the same 4 extra minutes on top of their 30-minute window.

  Migration

  In core/lib/kv/adapters/cloudflare-kv.ts, pass a cacheTtl when reading from the namespace:

  const ROUTES_READ_CACHE_TTL_SECONDS = 60 * 5;
  
  // RoutesKvNamespace
  get(key: string, options: { type: 'json'; cacheTtl?: number }): Promise<unknown>;
  
  // CloudflareKvAdapter.mget
  const value = await this.namespace.get(key, {
    type: 'json',
    cacheTtl: ROUTES_READ_CACHE_TTL_SECONDS,
  });

• Updated dependencies [4db7221]:

  • @bigcommerce/catalyst-client@1.0.4

[vercel]

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

Project	Deployment	Actions	Updated
catalyst	Ready	Preview	Oct 2, 2026 8:35pm UTC

[github-actions]

Bundle Size Report

Comparing against baseline from 75aa709 (2026-09-30).

No bundle size changes detected.

[github-actions]

Unlighthouse Comparison

Comparing this deployment's Unlighthouse scores against canary at 67585c9.

❌ Accessibility, SEO, and best practices regressions

These scores are stable between runs, so a drop fails the check. Open the full report to see which audits failed.

Route	Device	Category	Before	After
/your-first-blog-post/	Mobile	Best Practices	100	95

Details

Performance

Median per-route change against the baseline. Fails at a drop of 15 points on both devices.

Desktop	Mobile
−1.5	−1

Summary Score

Averages across the routes both scans reported, so a route that failed on one side doesn't skew them.

	Before Desktop	Before Mobile	After Desktop	After Mobile
Score	93	96	92	96

Category Scores

Category	Before Desktop	Before Mobile	After Desktop	After Mobile
Performance	75	88	73	87
Accessibility	96	97	96	97
Best Practices	100	100	100	100
SEO	100	100	100	100

Core Web Vitals

Metric	Before Desktop	Before Mobile	After Desktop	After Mobile
LCP	3.8 s	3.8 s	4.3 s	3.8 s
CLS	0.011	0.012	0.017	0.012
FCP	1.2 s	1.2 s	1.3 s	1.2 s
TBT	2 ms	2 ms	10 ms	5 ms
Max Potential FID	41 ms	46 ms	60 ms	50 ms
Time to Interactive	3.8 s	3.9 s	4.7 s	4.0 s

Full Unlighthouse report →