chore: add deployment for native hosting#2835
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1874cbb to
34ab11c
Compare
34ab11c to
55d7370
Compare
55d7370 to
080a96c
Compare
080a96c to
5deedda
Compare
bf2eea0 to
6751f5b
Compare
6751f5b to
3b845ca
Compare
3b845ca to
2d04f60
Compare
2d04f60 to
edb20d5
Compare
| - name: Install Catalyst CLI | ||
| run: pnpm add @bigcommerce/catalyst@alpha @opennextjs/cloudflare | ||
| working-directory: core |
There was a problem hiding this comment.
If this is our example gh-action, should we conditionally run this if it's already installed?
There was a problem hiding this comment.
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)
.github/workflows/native-hosting.yml
Outdated
| - 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 |
There was a problem hiding this comment.
I think the conversation we are having in Slack is crucial to this mess.
- I think building during the deploy command will resolve having two commands.
- The separation of CLI environment variables vs. Build-time environment variables vs. runtime environment variables is a topic of conversation.
edb20d5 to
3667a9b
Compare
47c486b to
e001d8e
Compare
e001d8e to
ae567fe
Compare
ae567fe to
4ed085f
Compare
4ed085f to
228ff5a
Compare
228ff5a to
5e2bc7a
Compare
- 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
5e2bc7a to
635906f
Compare
Bundle Size ReportComparing against baseline from No bundle size changes detected. |
Unlighthouse Performance Comparison — VercelComparing PR preview deployment Unlighthouse scores vs production Unlighthouse scores. Summary ScoreAggregate score across all categories as reported by Unlighthouse.
Category Scores
Core Web Vitals
|
What/Why?
Testing
Migration