Skip to content

chore: add deployment for native hosting#2835

Draft
chanceaclark wants to merge 2 commits intoalphafrom
chore/native-hosting-deployment
Draft

chore: add deployment for native hosting#2835
chanceaclark wants to merge 2 commits intoalphafrom
chore/native-hosting-deployment

Conversation

@chanceaclark
Copy link
Contributor

What/Why?

Testing

Migration

@changeset-bot
Copy link

changeset-bot bot commented Jan 22, 2026

⚠️ No Changeset found

Latest commit: 635906f

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

@vercel
Copy link

vercel bot commented Jan 22, 2026

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

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

Request Review

@chanceaclark chanceaclark force-pushed the chore/native-hosting-deployment branch 3 times, most recently from 1874cbb to 34ab11c Compare January 22, 2026 23:38
@chanceaclark chanceaclark force-pushed the chore/native-hosting-deployment branch from 34ab11c to 55d7370 Compare January 22, 2026 23:45
@chanceaclark chanceaclark force-pushed the chore/native-hosting-deployment branch from 55d7370 to 080a96c Compare January 22, 2026 23:50
@chanceaclark chanceaclark force-pushed the chore/native-hosting-deployment branch from 080a96c to 5deedda Compare January 22, 2026 23:57
@chanceaclark chanceaclark force-pushed the chore/native-hosting-deployment branch 2 times, most recently from bf2eea0 to 6751f5b Compare January 23, 2026 00:09
@chanceaclark chanceaclark force-pushed the chore/native-hosting-deployment branch from 6751f5b to 3b845ca Compare January 28, 2026 18:30
@chanceaclark chanceaclark force-pushed the chore/native-hosting-deployment branch from 3b845ca to 2d04f60 Compare January 28, 2026 20:06
@chanceaclark chanceaclark force-pushed the chore/native-hosting-deployment branch from 2d04f60 to edb20d5 Compare January 28, 2026 20:14
Comment on lines +28 to +30
- name: Install Catalyst CLI
run: pnpm add @bigcommerce/catalyst@alpha @opennextjs/cloudflare
working-directory: core
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this is our example gh-action, should we conditionally run this if it's already installed?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking about this earlier this morning, I say we keep it until the create-catalyst CLI installs Native Hosting deps for you; technically if someone follows documentation correctly, they won't need this step but right now there's not a huge risk to leaving it in (unless we ship a breaking change to the CLI on alpha, or something similar, which installing @whatever could actually break things)

Comment on lines +45 to +71
- name: Catalyst Build
run: pnpm run build
working-directory: core
# These environment variables are required for the build step to succeed
env:
AUTH_SECRET: ${{ secrets.NATIVE_HOSTING_AUTH_SECRET }}
BIGCOMMERCE_CHANNEL_ID: ${{ vars.NATIVE_HOSTING_BIGCOMMERCE_CHANNEL_ID }}
BIGCOMMERCE_STORE_HASH: ${{ vars.NATIVE_HOSTING_BIGCOMMERCE_STORE_HASH }}
BIGCOMMERCE_STOREFRONT_TOKEN: ${{ secrets.NATIVE_HOSTING_BIGCOMMERCE_STOREFRONT_TOKEN }}
BIGCOMMERCE_PROJECT_UUID: ${{ secrets.NATIVE_HOSTING_BIGCOMMERCE_PROJECT_UUID }}
OPEN_NEXT_DEBUG: true

- name: Catalyst Deploy
run: |
pnpm run deploy \
--secret BIGCOMMERCE_STORE_HASH=${{ vars.NATIVE_HOSTING_BIGCOMMERCE_STORE_HASH }} \
--secret BIGCOMMERCE_STOREFRONT_TOKEN=${{ secrets.NATIVE_HOSTING_BIGCOMMERCE_STOREFRONT_TOKEN }} \
--secret BIGCOMMERCE_CHANNEL_ID=${{ vars.NATIVE_HOSTING_BIGCOMMERCE_CHANNEL_ID }} \
--secret AUTH_SECRET=${{ secrets.NATIVE_HOSTING_AUTH_SECRET }} \
--secret OPEN_NEXT_ERROR_LOG_LEVEL=debug
working-directory: core
# These environment variables are for the deploy command only
# Added here to avoid polluting the run script with additional flags
env:
BIGCOMMERCE_ACCESS_TOKEN: ${{ secrets.NATIVE_HOSTING_BIGCOMMERCE_ACCESS_TOKEN }}
BIGCOMMERCE_PROJECT_UUID: ${{ secrets.NATIVE_HOSTING_BIGCOMMERCE_PROJECT_UUID }}
BIGCOMMERCE_STORE_HASH: ${{ vars.NATIVE_HOSTING_BIGCOMMERCE_STORE_HASH }} No newline at end of file
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the conversation we are having in Slack is crucial to this mess.

  1. I think building during the deploy command will resolve having two commands.
  2. The separation of CLI environment variables vs. Build-time environment variables vs. runtime environment variables is a topic of conversation.

chanceaclark and others added 2 commits March 18, 2026 13:46
- Remove pull_request trigger (no preview deployments)
- Add concurrency group to prevent parallel deploys
- Remove jq package.json mutation, use pnpm exec directly
- Add separate generate step for GraphQL types
- Fix env vars to CATALYST_* namespace for CLI commands
- Remove --framework flag (removed in alpha)
- Add --prebuilt to deploy (skip redundant build)
- Add BIGCOMMERCE_API_HOST for integration API
@github-actions
Copy link
Contributor

Bundle Size Report

Comparing against baseline from f3075ef (2026-03-18).

No bundle size changes detected.

@github-actions
Copy link
Contributor

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

Category Scores

Category Prod Desktop Prod Mobile Preview Desktop Preview Mobile
Performance 78 88 77 91
Accessibility 95 95 95 95
Best Practices 100 100 95 100
SEO 100 100 100 100

Core Web Vitals

Metric Prod Desktop Prod Mobile Preview Desktop Preview Mobile
LCP 3.5 s 3.9 s 3.4 s 3.5 s
CLS 0 0.039 0 0.002
FCP 1.1 s 1.2 s 1.2 s 1.2 s
TBT 0 ms 10 ms 0 ms 0 ms
Max Potential FID 50 ms 60 ms 50 ms 50 ms
Time to Interactive 3.5 s 3.9 s 3.4 s 3.6 s

Full Unlighthouse report →

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.

2 participants