Releases

Overview

Every time a workflow pushes an artifact, Fly creates a release. Fly understands what’s in it: what changed, who shipped it, and where it’s running. Find and manage any release by its content, not just a version number or run ID.

What is a Release?

A release is a semantic record of a workflow run. It captures everything Fly knows about what was built and shipped: what changed, who triggered it, what artifacts were produced, and where it’s running.

ComponentDescription
Release TitleA short, descriptive name for the release with a small icon that signals the type of change (e.g., “🛡️ CVE-2026-1234 Base Image Fix”). Fly generates this automatically. You can edit it at any time.
Release DescriptionA one-line summary of what the release contains. Shown as a hover preview in the release list. Fly generates this automatically. You can edit it at any time.
Release SummaryA full, structured breakdown of what changed: an overview, a list of changes, and any notes about breaking changes or migration steps. Shown on the release detail page.
Run NumberThe workflow run number, used as a technical identifier (e.g., #142).
Triggered ByThe GitHub user who ran the workflow.
ArtifactsAll packages and images produced by this release, with their types and versions.
CommitsAll commits included in this release, with links to GitHub.
Pull RequestsPRs merged in this release, with links to GitHub.
WorkflowThe GitHub Actions workflow that produced this release, with a link to the run.
Generation TimeWhen the release was created.
Environment BadgesThe environments this release is currently running in, shown as colored badges.

How to Generate a Release

A release is automatically created when:

  1. A GitHub Actions workflow runs
  2. The workflow has the Fly action configured
  3. The workflow successfully uploads at least one artifact to Fly Registry

Release List Page

Accessing Releases

  1. Navigate to Git Repositories
  2. Select a repository
  3. Click the Releases tab

Workflow Selector

If your repository has more than one configured workflow, a selector at the top of the page lets you focus on a single workflow or view all workflows together. The URL updates to reflect your selection, so you can bookmark or share a filtered view.

What You See Per Release

Each release is shown as a row with the following information:

FieldDescription
Release TitleThe release name with its icon and run number (e.g., 🛡️ #142 CVE-2026-1234 Base Image Fix).
Release DescriptionHover over a release to see a one-line preview of what changed, without navigating away.
Triggered ByThe GitHub user who triggered the workflow, shown as an avatar and username.
Generation TimeWhen the release was created, shown as relative time (e.g., “2 hours ago”).
Environment BadgesColored badges showing which environments this release is currently running in. If it hasn’t been deployed anywhere, no badges appear.
StatusA subtle indicator if the release was incomplete (e.g., the workflow failed after uploading some artifacts).

Release Detail Page

Click any release to open its detail page. This is the full picture of what that release contains and where it’s running.

Overview

  • Release Title: displayed prominently at the top. Click to edit.
  • Release Description: the one-line summary of what this release contains. Click to edit.
  • Repository: which repository this release belongs to, linked for easy navigation.
  • Generation Time: full timestamp with relative time.
  • Triggered By: the GitHub user who ran the workflow.

Release Summary

The full structured description of what changed: an overview, a “Changes” section with a list of what was added, updated, or removed, and optionally a “Notes” section for breaking changes or migration guidance.

Artifacts

All packages and images produced by this release, with their package types and versions.

Commits and Pull Requests

The Git changes included in this release: which PRs were merged and which commits were included, with links back to GitHub for full context.

Generating Workflow

The workflow that produced this release, with a direct link to the GitHub Actions run.

Editing a Release

You can update a release’s Title and Description at any time from the detail page. Your edits are saved and reflected immediately in semantic search. If you ask Fly to find a release by its updated name or description, it will find it.

Filters

FilterDescription
WorkflowShow releases from a specific workflow or all workflows.
Release AuthorFilter by the user who triggered the release.
Running on EnvironmentShow only releases currently deployed to a specific environment (e.g., Production, Staging).
Date RangeFilter by when the release was created: Last 24 hours, Last 7 days, Last 14 days.

Sorting

Releases are sorted by newest first by default. You can switch to oldest first.

Use the search bar to find releases by Title or Run Number.

For more powerful queries, use Chat Search: type a natural language question directly in the release list (e.g., “Which releases contain changes to the auth module?”) and Fly surfaces the relevant releases automatically.

Finding Releases via Fly Chat or Your IDE

You can search across all your releases using natural language from Fly Chat or your IDE (with Fly MCP).

Tip: When using your IDE, add “Fly release” to your query to help focus the search.

Example Queries

QueryFinds
“Find the release where I fixed the login bug”Releases mentioning login fixes
“Show me Jon’s last deployment”Most recent release triggered by Jon
“Releases from last week with API changes”Releases within a date range mentioning API
“Find the Fly release that broke production”Releases with issue-related keywords
“Fly release with Docker image updates”Releases that pushed Docker artifacts

Edited Titles and Descriptions are included in search results, so your customizations are always reflected.

Next Steps