# Diatreme > Release and deployment orchestration: a GitHub Marketplace composite action plus the hosted GitHub App broker that backs it. Canonical documentation for Diatreme, served at https://docs.magmamoose.com/diatreme/. The full text of every page below is at `llms-full.txt`. Each link is the page's markdown. The page itself is the same address without the `index.md`, or with `.html` in place of `.md`. ## Docs - [Using the action](https://docs.magmamoose.com/diatreme/action/index.md): This page is a task-oriented tour. The exhaustive input/output tables live in the repository README, this page does not duplicate them so they cannot drift. - [Architecture](https://docs.magmamoose.com/diatreme/architecture/index.md): Diatreme is two independent surfaces in one repo. They talk over HTTP and share no code. The action calls the broker's token endpoint; the broker never calls the action. - [Contributing](https://docs.magmamoose.com/diatreme/contributing/index.md): The authoritative contributor guide is AGENTS.md at the repo root. This page is a short orientation; AGENTS.md has the full rules. - [Glossary](https://docs.magmamoose.com/diatreme/glossary/index.md): Terms that appear in Diatreme's inputs, outputs, logs and errors. - [Promoting a release candidate to stable](https://docs.magmamoose.com/diatreme/how-to/promote-a-release-candidate/index.md): Release the build that was tested, not a rebuild of it. promote-from takes a prerelease tag and releases that exact image as its stable version: v1.5.0-rc.3 becomes v1.5.0, same commit, same image. - [Publishing a public Helm chart](https://docs.magmamoose.com/diatreme/how-to/publish-a-helm-chart/index.md): package-ecosystem: helm packages a chart and pushes it to an OCI registry in the same run that tags the release and promotes its image, so the chart and the image it points at come from one commit. Four opt-in extras turn that into a chart strangers can find and trust: a lint gate, a cosign signature, Artifact Hub's… - [Releasing a versioned application suite](https://docs.magmamoose.com/diatreme/how-to/release-a-versioned-suite/index.md): A suite repository can select the image versions of several applications without building those applications. Diatreme tags that selection, combines their published release notes, and publishes a suite GitHub Release with a release.json snapshot. Application Kubernetes resources can stay in their own repositories;… - [Releasing from release branches](https://docs.magmamoose.com/diatreme/how-to/release-from-release-branches/index.md): For teams that release on a schedule rather than on every merge. Features reach the main line through pull requests. When a release is due, the team cuts a release branch named after the version it chose, the branch's build goes to acceptance, and once it is signed off that same build goes to production. A production… - [Releasing several packages from one repository](https://docs.magmamoose.com/diatreme/how-to/release-several-packages/index.md): One repository, several independently versioned packages. tag-prefix is what keeps their version histories apart. - [Diatreme](https://docs.magmamoose.com/diatreme/index.md): Diatreme is a release/deployment orchestrator. It has two independent surfaces in one repository that communicate over HTTP, neither imports the other: - [Deployment](https://docs.magmamoose.com/diatreme/operations/deployment/index.md): Three things ship out of this repository on their own schedules: the composite action, the broker, and this site. - [Action reference](https://docs.magmamoose.com/diatreme/reference/action/index.md): Generated by scripts/gen_action_reference.py from action.yml. Edit the action, not this page. For the task-shaped version, see Using the action. - [Broker API](https://docs.magmamoose.com/diatreme/reference/broker-api/index.md): The broker is the GitHub App backend the action calls when auth-mode is public-app. The production Python/Lambda broker serves POST /token (the route the action uses). The retired Cloudflare Worker also served POST /sign, GET /releases, and POST /webhook; those are documented below for reference. Anything else returns… - [Broker configuration](https://docs.magmamoose.com/diatreme/reference/configuration/index.md): Everything the broker reads at runtime. You only need this page if you self-host a broker or operate the hosted one. Consumers of the action configure nothing here: they set action inputs, which are documented in the repository README. - [Errors](https://docs.magmamoose.com/diatreme/reference/errors/index.md): Every failure a Diatreme run can surface, what causes it, and what to do. The action fails hard: any broker fault exits the step non-zero, so a broken broker is a red X on the release rather than a silent skip. - [Limits and lifetimes](https://docs.magmamoose.com/diatreme/reference/limits/index.md): Caps, timeouts and TTLs built into both broker implementations (Python/Lambda and TypeScript/Cloudflare Worker). None of these are configurable per request. They're here so you can tell a limit from a bug. - [Security](https://docs.magmamoose.com/diatreme/security/index.md): Diatreme holds a GitHub App private key and mints short-lived, write-scoped installation tokens for other people's repositories. This page describes how it protects that, and what you're responsible for. - [Setup](https://docs.magmamoose.com/diatreme/setup/index.md): Pin to the floating major tag: - [The broker](https://docs.magmamoose.com/diatreme/worker/index.md): The GitHub App backend behind https://api.diatreme.magmamoose.com. It exists so callers don't have to register and run their own GitHub App: the action's default auth-mode: public-app exchanges an Actions OIDC token here for a short-lived installation token.