SyncTV Release

This repository coordinates tested releases across synctv-org/synctv and synctv-org/synctv-app.

Each component repository owns its build, signing, package publication, and GitHub Release. This repository owns release intent, cross-repository orchestration, immutable artifact resolution, and the final suite Release.

Release model

flowchart LR
  P["Release manifest commit"] --> V["Validate exact commits and versions"]
  V --> M["Push to main"]
  M --> B["Tag server repository"]
  M --> A["Tag app repository"]
  B --> BA["Server image, chart, and Release"]
  A --> AA["Signed app artifacts and Release"]
  BA --> L["Resolve image digest and write release lock"]
  AA --> L
  L --> R["Publish suite Release"]
  R --> N["Add app downloads to server Release"]

Loading

A release is authorized by adding exactly one immutable manifest under releases/ and merging it to main. The orchestrator creates component tags, waits for their existing workflows, and publishes release-lock.yml as the suite Release record. It performs no Rust or Flutter compilation.

Prepare a release

1. Copy examples/release.yml to releases/YYYY.MM.PATCH.yml.
2. Set each component to a full 40-character commit SHA.
3. Set versions and tags to the metadata already committed at those SHAs.
4. Confirm the server commit's synctv-web-ui/web-ui.production.toml pins the same App repository and commit as the manifest. Its production revision must equal that full commit SHA.
5. Commit the manifest directly to main and wait for Validate release manifests.
6. Approve the release Environment when approval is configured.

Run the same validation locally:

make validate

The workflow produces three public records:

• Server Release with app quick downloads, deployment documentation, server changes, container image digest, and Helm chart.
• App Release and its platform artifacts.
• Suite Release containing the resolved lock and links to both components.

Repository configuration

Create a GitHub App installed on synctv, synctv-app, and this repository. Grant it Contents: Read and write and Actions: Read. Configure these repository secrets:

Secret	Purpose
RELEASE_APP_ID	GitHub App ID
RELEASE_APP_PRIVATE_KEY	GitHub App private key
RELEASE_TOKEN	Bootstrap PAT fallback with repository and workflow access

The workflow prefers the GitHub App installation token. RELEASE_TOKEN supports initial setup and release testing before the GitHub App credentials are configured. Store it as a repository secret and rotate or remove it after the GitHub App is active.

Create a release GitHub Environment for optional approval and restrict deployment to main. Component signing and store credentials remain in their own repositories.

See the runbook for retries and recovery, and ADR-0001 for the production patterns behind this design.