Axon 911 Frontend Docs
    Loading navigation…
U
User
Switch to light mode
  1. Ci Cd
  3. Deployment

Deployment

What happens after a PR is opened and after it merges — Vercel previews, the trunk environment, and the manual path to production.

axon911-frontend deploys to Vercel. Each Module Federation shell and remote is its own Vercel project, and Vercel does every build. There are no Docker images, container registry pushes or ArgoCD syncs in this pipeline. This page is the short version; the full architecture and procedures are in docs/DEPLOY-VERCEL.mdopens in a new tab and docs/DEPLOY-VERCEL-RUNBOOK.mdopens in a new tab. Run pnpm mf:apps for the current list of deployables.
Three surfaces
A change reaches users through three surfaces: a PR preview, the trunk environment, and production. The runbook's environments tableopens in a new tab says when each updates, and the domain patterns for shells and remotes are in docs/DEPLOY-VERCEL.mdopens in a new tab. The shell resolves remote hostnames in the browser on every load, so any shell or remote can be promoted independently, in any order, as long as each stays compatible with the other's previous version. The deploy orderopens in a new tab section says when order matters.
Before merge: PR previews
pr-preview.ymlopens in a new tab ("Preview deployments") runs on pull_request_target. A trusted planning job decides which projects the PR affects, a deploy job creates Vercel preview deployments through the Vercel API, and a status job posts one comment per PR and a Preview deployments check. In a stack of PRs only the top builds a preview, unless a lower PR carries the Preview label (see Stacks: only the top buildsopens in a new tab). Previews get stable PR branch domains, and the domains are removed when the PR closes. The trust boundary, recovery steps and project provisioning are documented in .github/scripts/preview/README.mdopens in a new tab. The Preview deployments check is not required to merge. The queue's gtmq_* draft PRs skip planning and deployment unless they carry the Preview label, because each of those commits is what trunk builds after the merge.
At merge: the trunk environment
Merging goes through the Graphite merge queue (see PR Checks and the merge-queue skill). Normal trunk builds come from Vercel's Git integration. Every trunk push also runs the preview workflow's reconciliation, which provisions a new project or completes its handoff from PR-only previews to Git deployments. The Vercel Production Branch is manual-production, so a merge deploys only to the custom trunk environment, and automatic custom-domain assignment stays off. Trunk is where to validate a change against the trunk remotes before production.
Workflows that report after a merge (metrics, baselines, deploys) trigger on push to trunk. Graphite fast-forwards trunk, so GitHub sees a push and never a merge_group event.
Production: a manual promote
Production traffic moves only when someone promotes a trunk deployment, by dashboard or CLI. The runbook covers:
  • promoting a trunk deploymentopens in a new tab, which rebuilds with production environment variables;
  • rolling releasesopens in a new tab for gradual rollout;
  • rollbackopens in a new tab, with Instant Rollback, because a deployment that has already been promoted cannot be promoted again;
  • validationopens in a new tab and observabilityopens in a new tab.
Why this shape: a merge is cheap and reversible, so it deploys to trunk automatically. Reaching production domains is a separate, deliberate step, so each shell and remote can ship on its own schedule.
Other release paths
  • Published packages (@prepared911/ui, @prepared911/core and the rest of the Changesets allowlist): package-release-pr.yamlopens in a new tab opens the Version Packages PR from trunk, and package-publish-changesets.yamlopens in a new tab publishes. See docs/package-publishing.mdopens in a new tab.
  • The desktop app: desktop-release.ymlopens in a new tab. Standalone apps such as auth and storybook follow their own project settings.
Previous
CI/CD & deployment / PR Checks
Next
Colors
On this page
Three surfaces
Before merge: PR previews
At merge: the trunk environment
Production: a manual promote
Other release paths