Version Packages (integrations/makeswift)

[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 integrations/makeswift, this PR will be updated.

Releases

@bigcommerce/catalyst-makeswift@1.4.3

Patch Changes

• #2862 52207b6 Thanks @Codeseph! - fix: handle OPTIONS requests via MakeswiftApiHandler

• #2860 5097034 Thanks @jorgemoya! - Add explicit Makeswift SEO metadata support to public-facing pages. When configured in Makeswift, the SEO title and description will take priority over the default values from BigCommerce or static translations.

  The following pages now support Makeswift SEO metadata:

  • Home page (/)
  • Catch-all page (/[...rest])
  • Product page (/product/[slug])
  • Brand page (/brand/[slug])
  • Category page (/category/[slug])
  • Blog list page (/blog)
  • Blog post page (/blog/[blogId])
  • Search page (/search)
  • Cart page (/cart)
  • Compare page (/compare)
  • Gift certificates page (/gift-certificates)
  • Gift certificates balance page (/gift-certificates/balance)
  • Contact webpage (/webpages/[id]/contact)
  • Normal webpage (/webpages/[id]/normal)

  Migration steps

  Step 1: Add getMakeswiftPageMetadata function

  Add the getMakeswiftPageMetadata function to core/lib/makeswift/client.ts:

  + export async function getMakeswiftPageMetadata({ path, locale }: { path: string; locale: string }) {
  +   const { data: pages } = await client.getPages({
  +     pathPrefix: path,
  +     locale: normalizeLocale(locale),
  +     siteVersion: await getSiteVersion(),
  +   });
  +
  +   if (pages.length === 0 || !pages[0]) {
  +     return null;
  +   }
  +
  +   const { title, description } = pages[0];
  +
  +   return {
  +     ...(title && { title }),
  +     ...(description && { description }),
  +   };
  + }

  Export the function from core/lib/makeswift/index.ts:

    export { Page } from './page';
  - export { client } from './client';
  + export { client, getMakeswiftPageMetadata } from './client';

  Step 2: Update page metadata

  Each page's generateMetadata function has been updated to fetch Makeswift metadata and use it as the primary source, falling back to existing values. Here's an example using the cart page:

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

    import { getPreferredCurrencyCode } from '~/lib/currency';
  + import { getMakeswiftPageMetadata } from '~/lib/makeswift';
    import { Slot } from '~/lib/makeswift/slot';

    export async function generateMetadata({ params }: Props): Promise<Metadata> {
      const { locale } = await params;
  
      const t = await getTranslations({ locale, namespace: 'Cart' });
  +   const makeswiftMetadata = await getMakeswiftPageMetadata({ path: '/cart', locale });
  
      return {
  -     title: t('title'),
  +     title: makeswiftMetadata?.title || t('title'),
  +     description: makeswiftMetadata?.description || undefined,
      };
    }

  Apply the same pattern to the other pages listed above, using the appropriate path for each page (e.g., /blog, /search, /compare, etc.).

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
catalyst	Ready	Preview, Comment	Feb 9, 2026 11:34pm