Skip to content

sync integrations/makeswift with canary#2926

Merged
jorgemoya merged 3 commits intointegrations/makeswiftfrom
sync-integrations-makeswift
Mar 16, 2026
Merged

sync integrations/makeswift with canary#2926
jorgemoya merged 3 commits intointegrations/makeswiftfrom
sync-integrations-makeswift

Conversation

@jorgemoya
Copy link
Contributor

Summary

Merges canary into integrations/makeswift to bring the Makeswift integration up to date.

What came from canary

Conflict resolutions

  • core/app/[locale]/(default)/product/[slug]/page.tsx — kept both makeswift imports (getMakeswiftPageMetadata, ProductDetail from ~/lib/makeswift/components/product-detail) and canary's new getRecaptchaSiteKey import.
  • core/app/[locale]/(default)/webpages/[id]/contact/page.tsx — kept both getMakeswiftPageMetadata and the new getRecaptchaSiteKey import.
  • pnpm-lock.yaml — accepted canary's version then regenerated with pnpm install --no-frozen-lockfile.

Changeset cleanup

Removed .changeset/lazy-rivers-stare.md (targets @bigcommerce/catalyst-core, not @bigcommerce/catalyst-makeswift).


Do not squash or rebase-and-merge this PR. Use a true merge commit or rebase locally to preserve the merge base between canary and integrations/makeswift.

matthewvolk and others added 3 commits March 13, 2026 19:28
Simplify Stage 2 of the release process by including the
@bigcommerce/catalyst-makeswift changeset directly in the sync merge
commit instead of requiring a separate bump-version branch and PR.
Also update the tags section with explicit commands for both packages.
* added recaptcha v3

* update recaptcha package and make visible on forms

* linting

* make recaptcha optional for dynamic-form

* remove comments

* remove comments

* remove recaptcha provider since it wasn't used

* make recaptcha required if enabled and use getValue to retrieve token

* add types for react-google-recaptcha

* fix linting

* fix linting

* fix linting

* fix linting

* refactor(recaptcha): validate in form actions and separate parse from validate

- Add validateRecaptchaToken() to validate reCAPTCHA in form actions and
  return formErrors so Conform displays them (contact, review, register).
- Add getRecaptchaFromForm() to parse site key and token from FormData.
- Make validateRecaptchaToken() a pure function (siteKey, token, message)
  so validation is separate from form parsing and easier to test/reuse.
- Contact, review, and register actions: parse via getRecaptchaFromForm(),
  then validate via validateRecaptchaToken(), and pass token to mutations.

Made-with: Cursor

* fix linting

* remove client side logic and error handling

* rename validat function for recaptha token to assertRecaptchaTokenPresent

* remove unused recaptcha settings in graphql

* fix linting

* remove client side logic and validation for recaptcha

* remove unused properties from RecaptchaSettings interface

* remove unnecessary DynamicFormInner wrapper component

Made-with: Cursor

* remove unused failedLoginLockoutDurationSeconds and isEnabledOnCheckout from getReCaptchaSettings

Made-with: Cursor

* add changeset

* chore: add tests for recaptcha

---------

Co-authored-by: Jorge Moya <jorge.moya@bigcommerce.com>
# Conflicts:
#	core/app/[locale]/(default)/product/[slug]/page.tsx
#	core/app/[locale]/(default)/webpages/[id]/contact/page.tsx
#	pnpm-lock.yaml
@jorgemoya jorgemoya requested a review from a team as a code owner March 16, 2026 18:09
@vercel
Copy link

vercel bot commented Mar 16, 2026

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

Project Deployment Actions Updated (UTC)
catalyst Ready Ready Preview, Comment Mar 16, 2026 6:10pm

Request Review

@changeset-bot
Copy link

changeset-bot bot commented Mar 16, 2026

⚠️ No Changeset found

Latest commit: 4c5ff0e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@github-actions
Copy link
Contributor

Bundle Size Report

Comparing against baseline from 990727b (2026-03-16).

Metric Baseline Current Delta
Total JS 585.4 kB 590.1 kB +4.7 kB (+0.8%)

Per-Route First Load JS

Route Baseline Current Delta
/(default)/(auth)/change-password/page 593.3 kB 597.8 kB +4.5 kB (+0.8%)
/(default)/(auth)/login/forgot-password/page 592.4 kB 596.9 kB +4.5 kB (+0.8%)
/(default)/(auth)/login/page 593 kB 597.5 kB +4.5 kB (+0.8%)
/(default)/(auth)/register/page 594.4 kB 598.9 kB +4.5 kB (+0.8%)
/(default)/(faceted)/brand/[slug]/page 599.2 kB 603.7 kB +4.5 kB (+0.8%)
/(default)/(faceted)/category/[slug]/page 607.4 kB 611.9 kB +4.5 kB (+0.7%)
/(default)/(faceted)/search/page 599.2 kB 603.7 kB +4.5 kB (+0.8%)
/(default)/[...rest]/page 594.4 kB 598.9 kB +4.5 kB (+0.8%)
/(default)/account/addresses/page 596.9 kB 601.4 kB +4.5 kB (+0.8%)
/(default)/account/orders/[id]/page 592 kB 596.5 kB +4.5 kB (+0.8%)
/(default)/account/orders/page 593 kB 597.5 kB +4.5 kB (+0.8%)
/(default)/account/settings/page 596.4 kB 600.9 kB +4.5 kB (+0.8%)
/(default)/account/wishlists/[id]/page 601.7 kB 606.2 kB +4.5 kB (+0.7%)
/(default)/account/wishlists/page 596.4 kB 600.9 kB +4.5 kB (+0.8%)
/(default)/blog/[blogId]/page 594.4 kB 598.9 kB +4.5 kB (+0.8%)
/(default)/blog/page 595.1 kB 599.6 kB +4.5 kB (+0.8%)
/(default)/cart/page 601 kB 605.5 kB +4.5 kB (+0.7%)
/(default)/compare/page 595.7 kB 600.2 kB +4.5 kB (+0.8%)
/(default)/gift-certificates/balance/page 596.2 kB 600.7 kB +4.5 kB (+0.8%)
/(default)/gift-certificates/page 594.4 kB 598.9 kB +4.5 kB (+0.8%)
/(default)/gift-certificates/purchase/page 596.1 kB 600.6 kB +4.5 kB (+0.8%)
/(default)/page 594.4 kB 598.9 kB +4.5 kB (+0.8%)
/(default)/product/[slug]/page 607.5 kB 612 kB +4.5 kB (+0.7%)
/(default)/webpages/[id]/contact/page 597.5 kB 602 kB +4.5 kB (+0.8%)
/(default)/webpages/[id]/normal/page 594.9 kB 599.4 kB +4.5 kB (+0.8%)
/(default)/wishlist/[token]/page 598.4 kB 602.9 kB +4.5 kB (+0.8%)
/maintenance/page 590.9 kB 595.4 kB +4.5 kB (+0.8%)

Threshold: 5% increase. Routes with ⚠️ exceed the threshold.

@github-actions
Copy link
Contributor

github-actions bot commented Mar 16, 2026

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

Category Scores

Category Prod Desktop Prod Mobile Preview Desktop Preview Mobile
Performance 69 77 68 78
Accessibility 91 91 91 91
Best Practices 95 100 95 100
SEO 89 89 100 100

Core Web Vitals

Metric Prod Desktop Prod Mobile Preview Desktop Preview Mobile
LCP 6.3 s 5.9 s 5.3 s 5.8 s
CLS 0 0.039 0.001 0.039
FCP 1.1 s 1.1 s 1.1 s 1.1 s
TBT 40 ms 70 ms 20 ms 40 ms
Max Potential FID 120 ms 110 ms 80 ms 110 ms
Time to Interactive 8.9 s 6.0 s 6.4 s 9.0 s

Full Unlighthouse report →

@parthshahp
Copy link
Contributor

parthshahp commented Mar 16, 2026

Hey! So just for my understanding, the actual code in this PR has been approved previously when merging into canary, and this is just bringing the integrations/makeswift branch up to speed? So the "new" things in this PR should only be the resolved merge conflicts?

Also, is there any documentation on the catalyst dev process that talks about all of these things?

@chanceaclark
Copy link
Contributor

@parthshahp this claude skill + CONTRIBUTING.md might help get context on the current release process. But yes, it's just "rebasing"/merging the changes in so it's previously approved code.

@jorgemoya jorgemoya merged commit 4c5ff0e into integrations/makeswift Mar 16, 2026
18 of 19 checks passed
@jorgemoya jorgemoya deleted the sync-integrations-makeswift branch March 16, 2026 20:21
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.

5 participants