releases

For your own GitHub repo, publish a release with gh release create <tag> --repo <owner/repo> or the GitHub UI. floo deploys that release’s commit to prod once it is LIVE in dev. The floo GitHub App only reads customer repos; floo never writes to them. For a floo-hosted project or an app with no repo, use floo releases promote.

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": [
      {
        "release_number": 3,
        "tag": "v1.2.0",
        "commit_sha": "abc1234",
        "promoted_by": "you@example.com",
        "created_at": "2026-03-01T14:00:00Z",
        "deploy_id": "d5e6f7g8-...",
        "image_digest": "sha256:abcdef123456..."
      }
    ]
  }
}

show

Show one release: tag, commit, promoted by, deploy ID, image digest. RELEASE_ID is the release’s UUID.

floo releases show r1a2b3c4 --app my-app

Flags

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

JSON output

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

promote

Promote the latest LIVE dev deploy to production for a floo-hosted project created with floo projects, whose repo floo hosts without requiring a GitHub account, or for an app with no repo. floo deploys to prod; for a floo-hosted project it then publishes a release on the repo floo hosts. An app connected to your own GitHub repo is refused with PROMOTE_USE_GITHUB_RELEASE. The command returns the tag and release URL; floo deploys list --app my-app tracks the background deploy.

floo releases promote --app my-app

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. Each declared migrate_command runs as a one-off job with prod env vars before traffic shifts. A failure stops promotion and leaves the previous live revision serving. Keep the old code compatible with schema changes through expand-then-contract migrations. floo redeploy --skip-migrations has no effect on promote.
Routes. The shared app host ({app}.getfloo.app) and per-service hosts ({app}-{svc}.getfloo.app) 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/<managed-owner>/my-app/releases/tag/v1.2.1"
  }
}

release_url is set for floo-hosted projects and null for an app with no repo.

rollback

Use floo deploys rollback to restore a previous live deploy’s image without rebuilding:

floo deploys rollback my-app d1e2f3g4

The app and deploy ID are positional arguments. --preflight previews the operation; --yes is required in non-interactive runs. Rollback keeps current environment configuration and does not undo database migrations.

Errors

Code	Meaning
`NOT_AUTHENTICATED`	Run `floo auth login` first
`APP_NOT_FOUND`	No app with that name or ID
`PROMOTE_USE_GITHUB_RELEASE`	409: the app uses your own GitHub repo. The CLI suggests the exact `gh release create <tag> --repo <owner/repo>` command
`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

CLI

Config and runtime

Errors

API

list

Flags

JSON output

show

Flags

JSON output

promote

What happens during promote

Flags

Examples

JSON output

rollback

Errors

​list

​Flags

​JSON output

​show

​Flags

​JSON output

​promote

​What happens during promote

​Flags

​Examples

​JSON output

​rollback

​Errors

list

Flags

JSON output

show

Flags

JSON output

promote

What happens during promote

Flags

Examples

JSON output

rollback

Errors