Skip to content

Version Packages (canary)#3082

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

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

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

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@1.1.0

Minor Changes

  • #3084 aadaf27 Thanks @jorgemoya! - Add the catalyst domains claim command, which claims ownership of a custom domain that is already in use on another store. When you try to add a domain bound to a different store, catalyst domains add now prints the ownership-verification TXT record to publish; after publishing it, run catalyst domains claim <domain> to release the domain from the other store and bind it to your project.

  • #3089 8d9f9a9 Thanks @jorgemoya! - Add the catalyst domains transfer command, which moves a custom domain from one project to another project in the same store (the same-store counterpart to domains claim). Pass --to-project-uuid <uuid> to target a specific project, or omit it to pick the destination interactively from your store's projects. When catalyst domains add fails because the domain is already bound to another project in the store, it now points you at the exact domains transfer command to move it instead of surfacing the raw API error.

Patch Changes

  • #3088 ce03afb Thanks @jorgemoya! - Stop framing clear, user-actionable CLI errors as bugs to report. Validation errors, not-found and not-enabled responses, conflicts, and bad command input now print just the message and exit, instead of appending a Correlation ID and a "share this with BigCommerce support" prompt. That framing is now reserved for genuine server-side (5xx) failures and unexpected errors. Applies across the domains, project, channel, logs, and auth commands via a shared UserActionableError type.

@bigcommerce/create-catalyst@2.0.1

Patch Changes

@bigcommerce/catalyst-core@1.9.0

Minor Changes

  • #3083 2b7f2cc Thanks @jorgemoya! - Display product videos (YouTube) on the PDP in a dedicated section below the primary product content, mirroring the Stencil/Cornerstone layout. The Storefront GraphQL API exposes product videos as a { title, url } pair (Product.videos); Catalyst now fetches them and renders a featured player with a thumbnail strip (clicking a thumbnail swaps the featured video) using lite-youtube-embed — a lightweight facade that loads the YouTube player only when a shopper clicks. A small getYouTubeId() helper extracts the video id from the watch URL the API returns.

    Migration

    Additive — no breaking changes; existing PDP markup, the image gallery, and image pagination are unchanged. Forks adopting this manually need to:

    • add the lite-youtube-embed dependency;
    • request videos(first: 25) { edges { node { title url } } } on the PDP product query (product/[slug]/page-data.ts);
    • stream those videos and render the new ProductVideos section below ProductDetail (product/[slug]/page.tsx);
    • allow i.ytimg.com/vi/** in next.config.ts images.remotePatterns for poster thumbnails.
  • #3057 a763acc Thanks @bc-vivekaggarwal! - Wire promotion callouts into PDP and PLP pages using live data from the Storefront GraphQL API (featuredPromotions on the Product type).

    • PDP: stacked callout boxes render inline below the price, one per active promotion.
    • PLP (category, brand, search): each product card shows its first promotion inline below the price; if there are multiple, a "+N more" label appears within the same callout.

Patch Changes

  • #3076 c6b3b07 Thanks @chanceaclark! - Fix Account Settings failing to save for customers when a merchant-defined required custom customer field exists. BigCommerce revalidates required custom fields on every updateCustomer call, so Account Settings now renders and resubmits those fields (mirroring the existing Register/Address form-field support) instead of only supporting first name, last name, email, and company.

  • #3087 cb7d025 Thanks @jairo-bc! - Respect the Blog visibility setting (Control Panel > Storefront > Blogs) in the footer navigation. The Blog link no longer appears in the footer's "Navigate" section when Blog visibility is turned off.

@github-actions github-actions Bot requested a review from a team as a code owner July 6, 2026 20:23
@vercel

vercel Bot commented Jul 6, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
catalyst Ready Ready Preview, Comment Jul 10, 2026 2:50pm

Request Review

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor Author

Bundle Size Report

Comparing against baseline from c6b3b07 (2026-07-06).

No bundle size changes detected.

@github-actions

github-actions Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor Author

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 89 92 91 94

Category Scores

Category Prod Desktop Prod Mobile Preview Desktop Preview Mobile
Performance 76 88 73 82
Accessibility 95 98 95 92
Best Practices 100 100 100 100
SEO 88 88 100 100

Core Web Vitals

Metric Prod Desktop Prod Mobile Preview Desktop Preview Mobile
LCP 3.6 s 3.8 s 4.5 s 4.8 s
CLS 0.05 0 0.037 0
FCP 1.1 s 1.2 s 1.2 s 1.1 s
TBT 20 ms 0 ms 20 ms 0 ms
Max Potential FID 80 ms 40 ms 90 ms 50 ms
Time to Interactive 3.7 s 3.9 s 4.7 s 4.9 s

Full Unlighthouse report →

@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 2e19863 to 865ae79 Compare July 7, 2026 22:29
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 865ae79 to 9ffa584 Compare July 7, 2026 23:19
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 9ffa584 to d4383c6 Compare July 7, 2026 23:41
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from d4383c6 to 52ed33e Compare July 8, 2026 15:01
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 52ed33e to 0bc942b Compare July 8, 2026 19:47
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 0bc942b to 0cb6daa Compare July 8, 2026 19:53
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 0cb6daa to 384150c Compare July 8, 2026 20:25
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 384150c to 9581854 Compare July 8, 2026 21:23
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from 9581854 to ee90862 Compare July 8, 2026 22:41
@github-actions github-actions Bot force-pushed the changeset-release/canary branch from ee90862 to 254efb9 Compare July 10, 2026 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants