releases - floo

Manage releases and promote apps to production. Promoting from the CLI and cutting a GitHub release are the same operation: both take the latest live dev deploy to prod, and floo releases promote creates the GitHub release for you when a repo is connected.

list

List releases for an app.

floo releases list --app my-app

Flags

Flag	Description
`--app APP`	App name or UUID

JSON output

{
  "success": true,
  "data": {
    "releases": [
      {
        "id": "r1a2b3c4-...",
        "tag": "v1.2.0",
        "commit_sha": "abc1234",
        "promoted_by": "you@example.com",
        "deploy_id": "d5e6f7g8-...",
        "created_at": "2026-03-01T14:00:00Z"
      }
    ]
  }
}

show

Show details for a specific release (tag, commit, promoted by, deploy ID, image digest).

floo releases show r1a2b3c4 --app my-app

Flags

Flag	Description
`--app APP`	App name or UUID

JSON output

{
  "success": true,
  "data": {
    "id": "r1a2b3c4-...",
    "tag": "v1.2.0",
    "commit_sha": "abc1234",
    "promoted_by": "you@example.com",
    "deploy_id": "d5e6f7g8-...",
    "image_digest": "sha256:abcdef123456...",
    "created_at": "2026-03-01T14:00:00Z"
  }
}

promote

Promote the latest live dev deploy to production. Creates a GitHub release if GitHub is connected. The API accepts the promote and runs it in the background; the command returns the tag and release URL, and floo deploys list --app my-app shows the prod deploy as it progresses.

floo releases promote --app my-app

✓ Promoted my-app → prod (v1.2.1)
  Release: https://github.com/you/my-app/releases/tag/v1.2.1

What happens during promote

Image selection. Promote deploys the images from the latest live dev deploy. It rebuilds only when the prod environment has a build-time env var (VITE_*, NEXT_PUBLIC_*, or REACT_APP_*); then each service is built again from the source deploy’s archived source with the prod values as build arguments.
Migrations. For each service with a migrate_command in floo.app.toml, the command runs as a one-off job with prod env vars. On a promote that reuses the dev images, migrations run before any prod revision changes, and a failure marks the deploy FAILED and leaves production traffic where it was. On a promote that rebuilds because prod has build-time env vars, a migration failure is logged and the rollout continues. floo redeploy --skip-migrations has no effect on promote. See Run migrations through migrate_command.
Routes. The shared app host ({app}.on.getfloo.com) and per-service hosts ({app}-{svc}.on.getfloo.com) are upserted, so stale routes from before a service rename are corrected.
Access grants. The gateway is granted invoke access on public services, and the app identity on internal services.

Flags

Flag	Description
`--app APP`	App name or UUID
`--tag TAG`	Release tag (auto-generated if omitted, e.g., `v1.2.1`)

Examples

# Promote with auto-generated tag
floo releases promote --app my-app

# Promote with explicit tag
floo releases promote --app my-app --tag v2.0.0

# Agent workflow: promote and extract tag
floo releases promote --app my-app --json 2>/dev/null | jq -r '.data.tag'

JSON output

{
  "success": true,
  "data": {
    "tag": "v1.2.1",
    "release_url": "https://github.com/you/my-app/releases/tag/v1.2.1"
  }
}

release_url is empty when no GitHub repo is connected.

rollback

Roll back to a previous live deploy by re-pointing gateway routes at its image: no rebuild. This is the release-scoped equivalent of floo deploys rollback.

floo releases rollback --app my-app --to d1e2f3g4

Flags

Flag	Description
`--app APP`	App name or UUID
`--to ID`	Deploy ID to roll back to (the previous live deploy). Aliased as `--deploy`.
`--yes`	Skip the `y/N` prompt. Required in non-interactive contexts.

Rollback is tier-2 destructive: interactive mode prompts y/N; non-interactive runs require --yes.

Errors

Code	Meaning
`NOT_AUTHENTICATED`	Run `floo auth login` first
`APP_NOT_FOUND`	No app with that name or ID
`NO_DEV_DEPLOY`	Deploy to dev first before promoting
`NO_PROMOTABLE_SERVICES`	The latest live dev deploy has no image to promote
`RELEASE_TAG_EXISTS`	A release with that tag already exists. Use a different `--tag`
`RELEASE_NOT_FOUND`	No release with that ID

​list

​Flags

​JSON output

​show

​Flags

​JSON output

​promote

​What happens during promote

​Flags

​Examples

​JSON output

​rollback

​Flags

​Errors

list

Flags

JSON output

show

Flags

JSON output

promote

What happens during promote

Flags

Examples

JSON output

rollback

Flags

Errors