Skip to main content

​
CI/CD

This page is the published CI/CD policy for the repo.

​
Required checks

  • lint
  • docs lint
  • typecheck
  • tests
  • builds
  • Mintlify link validation and docs build validation

​
Planned hardening gates

These are intended additions, but they are not yet part of the default repo contract:
  • production container builds
  • migration validation
  • dependency review once the repository has the required GitHub security features enabled
  • secret scanning

​
CI hygiene follow-ups

  • Treat GitHub Actions Node.js 20 actions are deprecated annotations as maintenance work, not release blockers when checks are otherwise green. The repo runtime remains Node >=20, while workflows should keep action versions current and use the configured CI Node version.
  • When the annotation appears, identify the action emitting it, upgrade to a Node 24-compatible major version when available, rerun the affected workflow, and note the result in release or operations follow-up notes.
  • Do not route docs deploys through Vercel; Mintlify deploys from main after docs checks pass.

​
Branch policy

  • protected main
  • review required
  • green checks required
  • no direct pushes

​
Release policy

  • semver for intentional releases
  • build identity separate from semver
  • release notes from merged work
  • rollback notes in behavior-changing PRs