Releases

The Releases page lets you trigger release workflows on your repositories from a UI instead of from the GitHub Actions tab. The big win: the right workflow is preselected, the right inputs are validated, and every release shows up in one feed.

Adding a repository

Click Add repository and pick one your GitHub App installation can see. Autopilot will:

1. List the workflows in .github/workflows/ that look like release pipelines (anything that has workflow_dispatch and matches common release naming).
2. Let you pick a default workflow — the one that should run when you click "Release".
3. Save the configuration.

You can change the default workflow at any time, or remove a repository to take it off the list.

Triggering a release

Open a repository's detail page and you'll see:

• The default release workflow.
• The inputs that workflow accepts (version, tag, channel, etc.) — these come straight from the workflow's workflow_dispatch.inputs definition.
• Any required inputs marked accordingly.

Fill in the form and click Run release. Autopilot calls the GitHub workflow_dispatch API, then polls the run until it completes. The run shows up in your repository's Actions view as well.

Release files

If your release workflow uploads artifacts (binaries, build outputs, signed packages), Autopilot keeps a registry of them so you can find a specific release's outputs without trawling through Actions. Old release files are cleaned up on a cron schedule to keep storage reasonable.