What shipped between November 6 and 13
BigCommerce published two minor Catalyst releases and two CLI releases in eight days. According to the Catalyst releases page on GitHub, catalyst-core 1.14.0 and Catalyst CLI 1.6.0 landed on November 6. On November 13 came catalyst-core 1.15.0, CLI 1.6.1 and matching versions of the Makeswift and B2B Makeswift packages.
Catalyst is BigCommerce’s open source Next.js storefront for headless builds. If you run one, the release you should not skip is 1.14.0. It moves Catalyst to Next.js 16.4.3, which takes storefronts off versions affected by a next/og vulnerability, CVE-2026-94545.
Catalyst 1.14.0: pick lists, tracing and a Next.js security update
The 1.14.0 release notes list several changes that shoppers will notice.
- Items added through a pick list option now show in the cart under their parent line item, with the option’s label and their own selected options.
- Filtering by a parent category on brand and search pages now includes products assigned only to its sub-categories.
- Product list pages hide the filters column when there are no filters, and the cart quantity column has a fixed width so long backorder messages wrap.
- Analytics providers start before the first event, so Google Analytics no longer calls
gtagbefore it exists.
There is also a tracing fix for anyone hosting on Cloudflare Workers, including BigCommerce’s own Storefront Hosting. @vercel/otel failed to load on Workers, so those storefronts produced no OpenTelemetry spans at all. instrumentation.ts now detects the Workers runtime and sends spans to Workers tracing. Other runtimes still use @vercel/otel, now loaded lazily.
The upgrade notes are short. No environment variables changed. If you maintain your own translations, add the Cart.includedItems message. If you customized instrumentation.ts, keep your registerOTel() call behind the new Workers check and import @vercel/otel lazily.
Catalyst 1.15.0: mobile menu selects and fewer lost cart changes
The 1.15.0 release replaces the language and currency dropdowns in the mobile menu with labelled native selects that open the phone’s own picker. The currency select now appears on single-language stores too. Desktop keeps the dropdowns.
The more important fix is less visible. Cart, product, compare and wishlist sections were remounting when their analytics data finished streaming, which could throw away queued cart changes and add-to-cart results. That is fixed. Add-to-cart and remove-from-cart analytics events that fire before the data arrives are now held and sent once it does. Before this release they were dropped. If your add-to-cart numbers in analytics have looked low against orders, retest after the upgrade.
If you customized the mobile dropdowns, the release notes ask you to port those changes to the new MobileLocaleSelect and MobileCurrencySelect components. Navigation takes two new optional props, localeLabel and currencyLabel. Both releases also add agent skills to the repository for coding assistants, such as verify-catalyst, which drives the storefront in a browser and attaches screenshots, video and traces to pull requests.
CLI 1.6.0 changes how Storefront Hosting builds and deploys
Storefront Hosting is still in closed beta, according to the Catalyst CLI reference, so most of these changes only reach teams in that program. Two of them can change what goes live.
First, --env-path is now the only environment source. The November 12 changelog says catalyst build reads only that file and ignores .env.local and .env. catalyst deploy --env-path sends those variables to the deployment, overriding anything saved with catalyst env add. A per-deploy --secret still wins over both. A deploy script that passes an old env file could now overwrite values you set by hand.
Second, setup no longer renames proxy.ts to middleware.ts. The CLI pins @opennextjs/cloudflare 1.20.15, which bundles proxy.ts directly, and builds default to Wrangler 4.156.0. Projects set up with older CLIs keep middleware.ts and still work. If catalyst upgrade restores proxy.ts next to it, the CLI offers to delete middleware.ts, so move your edits into proxy.ts before you accept. catalyst deploy also reconnects when its status stream drops. It used to crash, or report success before the deployment had finished. CLI 1.6.1 on November 13 corrected help text.
How we would plan the upgrade
We would take 1.14.0 and 1.15.0 together on a branch, because the Next.js change is the reason to move this month. Run catalyst upgrade, which merges the new version into your project and writes conflict markers where it cannot. Resolve them in the files you have customized (navigation, header, cart and instrumentation are the likely ones) and add the new translation messages.
On a preview deployment, test a pick list product through to checkout, switch currency on a phone, and add and remove items quickly on a slow connection. If you are on Storefront Hosting, check your deploy scripts for --env-path and compare the deployed variables against what you expect before you point a channel at the new build.





