Skip to content

Version Packages (canary)#2961

Open
github-actions[bot] wants to merge 1 commit into
canaryfrom
changeset-release/canary
Open

Version Packages (canary)#2961
github-actions[bot] wants to merge 1 commit into
canaryfrom
changeset-release/canary

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot commented Mar 30, 2026 •
edited
Loading

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.2

Patch Changes

  • #3018 f4216a6 Thanks @parthshahp! - Fix client.fetch so that custom headers passed via fetchOptions.headers properly override the client's default headers. Headers are now built via a Headers object using .set(), so case-insensitive overrides work as expected.

@bigcommerce/catalyst-core@1.7.0

Minor Changes

  • #2989 518d20a Thanks @jorgemoya! - Restore locale-aware lang attribute on the root <html> tag. The previous root layout hardcoded lang="en" for all locales; ownership of <html>/<body> now lives in app/[locale]/layout.tsx so lang={locale} reflects the active locale. The root app/layout.tsx is now a passthrough, and app/not-found.tsx is self-sufficient (renders its own <html>/<body>) to preserve the branded 404 for non-localized requests.

  • #2825 7b38d98 Thanks @chanceaclark! - Add GraphQL proxy to enable client-side GraphQL requests through the storefront. This proxy forwards requests from allowed clients (such as checkout-sdk-js) to the BigCommerce Storefront API using a dedicated unauthenticated storefront token for API authorization, while still passing through the customer access token for customer-specific data. No browser cookies are forwarded.

    Migration

    Step 1: Add environment variable

    Add a BIGCOMMERCE_STOREFRONT_UNAUTHENTICATED_TOKEN to your .env.local. This should be a storefront API token scoped for client-side proxy use with minimal permissions.

    Step 2: Create proxy

    Create a new file core/proxies/with-graphql-proxy.ts:

    import { NextResponse, URLPattern } from 'next/server';
import { z } from 'zod';

import { auth } from '~/auth';
import { client } from '~/client';

import { type ProxyFactory } from './compose-proxies';

const ALLOWED_REQUESTERS = ['checkout-sdk-js'];
const graphqlPathPattern = new URLPattern({ pathname: '/graphql' });

const bodySchema = z.object({
  query: z.unknown(),
  variables: z.record(z.unknown()).default({}),
});

export const withGraphqlProxy: ProxyFactory = (next) => {
  return async (request, event) => {
    // Only handle /graphql path
    if (!graphqlPathPattern.test(request.nextUrl.toString())) {
      return next(request, event);
    }

    const requester = request.headers.get('x-catalyst-graphql-proxy-requester');

    // Validate required header
    if (!requester || !ALLOWED_REQUESTERS.includes(requester)) {
      return next(request, event);
    }

    // Only handle POST requests
    if (request.method !== 'POST') {
      return new NextResponse('Method not allowed', { status: 405 });
    }

    // Wrap in auth to get customer access token for customer-specific data
    return auth(async (req) => {
      try {
        // Parse incoming GraphQL request body
        const body: unknown = await req.json();
        const { query, variables } = bodySchema.parse(body);

        if (!query) {
          return NextResponse.json({ error: 'Missing query' }, { status: 400 });
        }

        // Get customer access token if authenticated
        const customerAccessToken = req.auth?.user?.customerAccessToken;

        // Proxy the request using the existing client with an unauthenticated storefront token
        const response = await client.fetch({
          document: query,
          variables,
          customerAccessToken,
          fetchOptions: {
            headers: {
              Authorization: `Bearer ${process.env.BIGCOMMERCE_STOREFRONT_UNAUTHENTICATED_TOKEN}`,
            },
            next: { revalidate: 0 },
          },
        });

        return NextResponse.json(response);
      } catch (error) {
        // eslint-disable-next-line no-console
        console.error(error);

        return NextResponse.json(error, { status: 500 });
      }
      // @ts-expect-error auth() overload expects middleware return type, but we return NextResponse directly for the proxy
    })(request, event);
  };
};

    Step 3: Register proxy

    Update core/proxy.ts to include the new proxy in the composition chain:

      import { composeProxies } from './proxies/compose-proxies';
  import { withAnalyticsCookies } from './proxies/with-analytics-cookies';
  import { withAuth } from './proxies/with-auth';
  import { withChannelId } from './proxies/with-channel-id';
+ import { withGraphqlProxy } from './proxies/with-graphql-proxy';
  import { withIntl } from './proxies/with-intl';
  import { withRoutes } from './proxies/with-routes';

  export const proxy = composeProxies(
    withAuth,
    withAnalyticsCookies,
    withIntl,
    withChannelId,
+   withGraphqlProxy,
    withRoutes,
  );

    The withGraphqlProxy proxy should be placed after withChannelId and before withRoutes in the chain.

Patch Changes

  • #3002 24cc310 Thanks @bc-alexsaiannyi! - Fix cart summary Discounts row not showing manual discounts applied via the Management Checkout API

  • #2976 a85fa42 Thanks @jorgemoya! - Add X-Correlation-ID header to all GraphQL requests. Each page render gets a stable UUID that persists across all fetches within the same render, enabling easier request tracing in server logs.

  • #3021 4e44415 Thanks @mfaris9! - Default brand PLP sort to featured to honor the merchant's product sort order.

  • #2964 d00beeb Thanks @chanceaclark! - Prevent breadcrumb array mutation on cached web pages by spreading the React cache() result before reversing, and fix an off-by-one in truncateBreadcrumbs that incorrectly truncated arrays exactly at the target length. Also defer ProductReviewSchema to client-only rendering to avoid a DOMPurify SSR crash.

  • #3005 37e0a7c Thanks @mfaris9! - Fix formField.required mismatch for checkbox-group fields in DynamicForm. The schema branch was missing .optional() for non-required checkbox groups.

  • #3013 9aacfdc Thanks @chanceaclark! - Pass the customer access token through route resolution and the normal/contact webpage queries so customer-restricted web pages are accessible (and appear in navigation) for authenticated customers. The with-routes proxy is now wrapped in auth(), and webpage page-data queries switch to an uncached fetch when a customer token is present.

  • #2963 a8dd99e Thanks @chanceaclark! - Fix DynamicForm not rendering hidden field types, which caused pageEntityId to be NaN on contact form submission.

  • #3014 a792a86 Thanks @parthshahp! - TRAC-276 translate the gift certificate line item title in cart, order list, and order details. Previously the title was rendered as the raw English "{amount} Gift Certificate" string stored on the BigCommerce backend; it is now rendered from the existing Cart.GiftCertificate.giftCertificate translation key, with the amount shown in the separate price column (the order list view now populates price/totalPrice for gift certificates, which were previously empty).

  • #3008 77c8e8d Thanks @bc-svc-local! - Update translations.

  • #2959 4870221 Thanks @bc-svc-local! - Update translations.

  • #2987 e18feb6 Thanks @bc-svc-local! - Update translations.

  • Updated dependencies [f4216a6]:

    • @bigcommerce/catalyst-client@1.0.2

@github-actions github-actions Bot requested a review from a team as a code owner March 30, 2026 17:55
@vercel
Copy link
Copy Markdown

vercel Bot commented Mar 30, 2026 •
edited
Loading

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

Project Deployment Actions Updated (UTC)
catalyst Ready Ready Preview, Comment May 21, 2026 2:00pm

Request Review

@github-actions
Copy link
Copy Markdown
Contributor Author

github-actions Bot commented Mar 30, 2026 •
edited
Loading

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 93 92 95

Category Scores

Category Prod Desktop Prod Mobile Preview Desktop Preview Mobile
Performance 77 88 71 79
Accessibility 95 98 95 98
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.5 s 3.8 s 4.5 s 5.7 s
CLS 0.001 0.056 0.04 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 40 ms 40 ms 50 ms 40 ms
Time to Interactive 3.6 s 3.8 s 4.5 s 5.7 s

Full Unlighthouse report →

@github-actions github-actions Bot force-pushed the changeset-release/canary branch from be1aaee to ad37350 Compare March 31, 2026 15:38
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from ad37350 to 9be4b1c Compare April 1, 2026 17:51
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 9be4b1c to 3f5158c Compare April 14, 2026 18:54
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 3f5158c to 7388a7e Compare April 14, 2026 23:16
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 7388a7e to f746d18 Compare April 23, 2026 23:03
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from f746d18 to 2c5a264 Compare April 24, 2026 15:44
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 2c5a264 to 1bbce19 Compare April 24, 2026 16:10
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 1bbce19 to 0b6e26c Compare April 27, 2026 20:34
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 0b6e26c to c45e42c Compare April 28, 2026 20:38
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from c45e42c to ccbc036 Compare April 30, 2026 17:17
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from ccbc036 to 85a5e46 Compare April 30, 2026 21:11
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 85a5e46 to 78faf77 Compare May 6, 2026 21:58
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 78faf77 to 1c596f6 Compare May 8, 2026 15:32
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 1c596f6 to f0e18bc Compare May 11, 2026 21:47
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from f0e18bc to 2232519 Compare May 12, 2026 06:53
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 2232519 to 63759e9 Compare May 13, 2026 16:50
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 63759e9 to 8adff3d Compare May 13, 2026 16:59
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 8adff3d to 9d490e1 Compare May 14, 2026 19:35
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 9d490e1 to 5e7e701 Compare May 15, 2026 15:36
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 5e7e701 to 4baaad9 Compare May 18, 2026 16:43
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 4baaad9 to 0c12ce0 Compare May 19, 2026 17:27
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 0c12ce0 to 288312d Compare May 19, 2026 20:13
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 288312d to 756f3da Compare May 21, 2026 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants