Skip to content

Releases: bigcommerce/catalyst

@bigcommerce/[email protected]

13 Nov 15:46
Compare
Choose a tag to compare

Minor Changes

Patch Changes

@bigcommerce/[email protected]

13 Nov 15:46
Compare
Choose a tag to compare

Minor Changes

@bigcommerce/[email protected]

12 Nov 16:00
Compare
Choose a tag to compare

Patch Changes

@bigcommerce/[email protected]

12 Nov 16:00
Compare
Choose a tag to compare

✨ This release updates to Next.js v15 ✨

Minor Changes

Patch Changes

@bigcommerce/[email protected]

12 Nov 16:00
Compare
Choose a tag to compare

Minor Changes

@bigcommerce/[email protected]

05 Nov 22:37
a8da829
Compare
Choose a tag to compare

Minor Changes

  • #1541 20c08da Thanks @matthewvolk! - Introduce an additional project creation scenario in which projects can be created without prompts if the CLI is provided with a valid --store-hash, --channel-id, and --storefront-token

@bigcommerce/[email protected]

04 Nov 17:12
d5abd43
Compare
Choose a tag to compare

Minor Changes

  • #1262 0c2023b Thanks @chanceaclark! - Generates a storefront token when using the CLI to init or create a Catalyst storefront.

  • #1262 0c2023b Thanks @chanceaclark! - Remove generating a customer impersonation token as we are using the API Token + Customer Access Token approach"

@bigcommerce/[email protected]

04 Nov 17:12
d5abd43
Compare
Choose a tag to compare

🔐 Update to GraphQL Authentication which solves checkout issues & improves security

We have created a new form of authentication for our GraphQL Storefront API which improves our security posture and solves session synchronization issues with headless checkouts.

Our new Customer Access Token for GraphQL is documented here

This update changes Catalyst to use normal GraphQL tokens and Customer Access Tokens in lieu of Customer Impersonation Tokens. You will need to do a one-time regeneration of your GraphQL token as part of the upgrade. New storefronts created via the CLI will provision appropriate tokens automatically, and existing apps can be updated by running the init command.

The benefit you’ll get is an improved security posture, and a better hosted checkout experience including:

  • Logged-in customers maintaining their login state through to checkout (without having to use Customer Login API)
  • A synchronized session between storefront & checkout; logging out in one place will log you out in both places
  • Support for more security-sensitive features we will add to Catalyst in the future, such as Saved Payment Methods

Minor Changes

  • #1262 0c2023b Thanks @chanceaclark! - Removes all usages of the customer impersonation token. Also updates the docs to correspond with the Storefront API Token.

  • #1262 0c2023b Thanks @chanceaclark! - Allows the ability to consume a storefront token. This new token will allow Catalyst to create customerAccessToken's whenever a user logs into their account. This change doesn't include consuming the either token, only adding the ability to pass it in.

Patch Changes

@bigcommerce/[email protected]

04 Nov 13:56
3dc9aa8
Compare
Choose a tag to compare

Patch Changes

@bigcommerce/[email protected]

04 Nov 17:12
d5abd43
Compare
Choose a tag to compare

Minor Changes

  • #1262 0c2023b Thanks @chanceaclark! - Removes all usages of the customer impersonation token. Also updates the docs to correspond with the Storefront API Token.

  • #1262 0c2023b Thanks @chanceaclark! - Allows the ability to consume a storefront token. This new token will allow Catalyst to create customerAccessToken's whenever a user logs into their account. This change doesn't include consuming the either token, only adding the ability to pass it in.