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-core@1.4.3

Patch Changes

• #2852 a7395f1 Thanks @chanceaclark! - Uses regular dompurify (DP) instead of isomorphic-dompurify (IDP), because IDP requires JSDOM. JSDOM doesn't work in edge-runtime environments even with nodejs compatibility. We only need it on the client anyways for the JSON-LD schema, so it doesn't need the isomorphic aspect of it. This also changes core/app/[locale]/(default)/product/[slug]/_components/product-review-schema/product-review-schema.tsx to be a client-component to enable `dompurify to work correctly.

  Migration

  1. Remove the old dependency and add the new:

  pnpm rm isomorphic-dompurify
  pnpm add dompurify -S

  2. Change the import in core/app/[locale]/(default)/product/[slug]/_components/product-review-schema/product-review-schema.tsx:

  - import DOMPurify from 'isomorphic-dompurify';
  +// eslint-disable-next-line import/no-named-as-default
  +import DOMPurify from 'dompurify';

  3. Add the 'use client'; directive to the top of core/app/[locale]/(default)/product/[slug]/_components/product-review-schema/product-review-schema.tsx.

• #2844 74dee6e Thanks @jordanarldt! - Update forms to translate the form field validation errors

  Migration

  Due to the amount of changes, it is recommended to just use the PR as a reference for migration.

  Detailed migration steps can be found on the PR here:
  chore(catalyst): CATALYST-1267 Translate form field errors #2844

• #2858 0633612 Thanks @jorgemoya! - Use state abbreviation instead of entityId for cart shipping form state values. The shipping API expects state abbreviations, and using entityId caused form submissions to fail. Additionally, certain US military states that share the same abbreviation (AE) are now filtered out to prevent duplicate key issues and ambiguous submissions.

  Migration steps

  Step 1: Add blacklist for states with duplicate abbreviations

  Certain US states share the same abbreviation (AE), which causes issues with the shipping API and React select dropdowns. Add a blacklist to filter these out.

  Update core/app/[locale]/(default)/cart/page.tsx:

    const countries = shippingCountries.map((country) => ({
      value: country.code,
      label: country.name,
    }));
  
  + // These US states share the same abbreviation (AE), which causes issues:
  + // 1. The shipping API uses abbreviations, so it can't distinguish between them
  + // 2. React select dropdowns require unique keys, causing duplicate key warnings
  + const blacklistedUSStates = new Set([
  +   'Armed Forces Africa',
  +   'Armed Forces Canada',
  +   'Armed Forces Middle East',
  + ]);
  
    const statesOrProvinces = shippingCountries.map((country) => ({

  Step 2: Use state abbreviation instead of entityId

  Update the state mapping to use abbreviation instead of entityId, and apply the blacklist filter for US states.

  Update core/app/[locale]/(default)/cart/page.tsx:

    const statesOrProvinces = shippingCountries.map((country) => ({
      country: country.code,
  -   states: country.statesOrProvinces.map((state) => ({
  -     value: state.entityId.toString(),
  -     label: state.name,
  -   })),
  +   states: country.statesOrProvinces
  +     .filter((state) => country.code !== 'US' || !blacklistedUSStates.has(state.name))
  +     .map((state) => ({
  +       value: state.abbreviation,
  +       label: state.name,
  +     })),
    }));

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
catalyst	Ready	Preview, Comment	Feb 4, 2026 3:13pm