> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tuturuuu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# CI/CD Pipelines

> High-level CI/CD overview, with current operational runbooks linked from one place.

This page is the entry point for CI/CD. The day-to-day operational detail now lives
in the dedicated DevOps pages below so the docs stay current as workflows change.

## Read Next

* [DevOps & Deployment Overview](/build/devops/overview)
* [Environments & Release Flow](/build/devops/environments-release-flow)
* [Web Docker Deployment](/build/devops/web-docker-deployment)
* [GitHub Actions Runbook](/build/devops/github-actions-runbook)
* [Secrets & Configuration](/build/devops/secrets-and-configuration)

## Current CI/CD Shape

Tuturuuu currently automates:

* Vercel preview deployments for non-`production` branches
* Vercel production deployments from the `production` branch
* Independent Vercel preview and production deployments for satellite apps such as `apps/cms`
* Affected-app gating for Vercel deployments before dependency install, build, or deploy work
* Supabase staging migrations driven from `main` and production migrations driven from `production`
* Docker parity and image validation for the self-hosted web runtime
* Modal deployment for `apps/discord`
* Mobile build artifact generation
* Package publishing to npm
* Quality, lint, type, test, and security checks

## Important Repo Conventions

* `ci-check.yml` reads `tuturuuu.ts` and can disable an individual workflow centrally.
* Vercel workflows use `tuturuuu.ts` app metadata and workspace `workspace:*` dependency closures to run only affected app deploys.
* `bun.lock` changes run all Vercel app deploys because lockfile ownership is ambiguous without a source or manifest path.
* Manual `workflow_dispatch` runs enabled workflows even when changed paths would otherwise be unaffected.
* Several deploy workflows intentionally skip if a newer commit already exists on the target branch.
* Database migrations are not treated the same as app deploys; staging and production each have explicit prerequisite logic, with staging now sourced from `main`.
* Docker changes are guarded by `docker-setup-check.yaml`, including dev and production image builds.

## When To Use This Page

Use this page for orientation. Use the DevOps pages for the runbook you actually need
while operating the system.