chore(ci): pass channel-specific env vars to vercel deploy#2834
Merged
matthewvolk merged 3 commits intocanaryfrom Jan 26, 2026
Merged
chore(ci): pass channel-specific env vars to vercel deploy#2834matthewvolk merged 3 commits intocanaryfrom
matthewvolk merged 3 commits intocanaryfrom
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
matthewvolk
force-pushed
the
CATALYST-1652-deploy-with-env-for-different-channels
branch
from
66ea87e to
d314cf4
Compare
replace eval with bash arrays, add timeouts, improve secret handling
Contributor
Author
|
Added the following vars/secrets:
|
jorgemoya
approved these changes
Jan 23, 2026
matthewvolk
deleted the
CATALYST-1652-deploy-with-env-for-different-channels
branch
jamesqquick
pushed a commit
that referenced
this pull request
Feb 11, 2026
* chore(ci): pass channel-specific env vars to vercel deploy * chore(ci): harden deploy workflow security replace eval with bash arrays, add timeouts, improve secret handling * chore(ci): add b2b env vars to deploy workflow
chanceaclark
pushed a commit
that referenced
this pull request
Apr 27, 2026
* chore(ci): pass channel-specific env vars to vercel deploy * chore(ci): harden deploy workflow security replace eval with bash arrays, add timeouts, improve secret handling * chore(ci): add b2b env vars to deploy workflow
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What/Why?
Updates the GitHub Actions deploy workflow to pass channel-specific environment variables to Vercel deployments. Previously, the workflow only parsed the tag to determine the deployment domain. Now it also:
env_prefixbased on package name (CORE,MAKESWIFT, orB2B_MAKESWIFT)BIGCOMMERCE_CHANNEL_IDandBIGCOMMERCE_STOREFRONT_TOKENfrom channel-specific secretsMAKESWIFT_SITE_API_KEYfor Makeswift-based deploymentsThis allows each deployment channel to use its own BigCommerce store configuration rather than relying on environment variables that may already be set in Vercel.
Also fixes a typo in the job name (
{{ github.ref_name }}→${{ github.ref_name }}).Testing
This change affects the CI deploy workflow. To test:
Migration
This change adds a new workflow file. No migration needed for developers with forks—this file can be accepted as-is or customized to match your own deployment secrets.