# Releases

> Bundle done issues into a shipped release from the command line.

```bash
getresolved release <action> [...]
# Alias: `releases`
```

**Actions** *(aliases in parens)*: `list` (`ls`), `show` (`view`, `get`), `create` (`new`), `help`.

A release groups one or more `done` issues so customers linked to the source conversations can be notified that their reports shipped. Linking an issue to a release flips that issue's status to `released`.

## List

```bash
getresolved release list
getresolved release list --product=<id> --limit=20
```

**Filters**: `--product=<id>`, `--limit=<n>`, `--offset=<n>`.

## Show

```bash
getresolved release show <id>
```

## Create

```bash
getresolved release create --title="v1.4 — mobile fixes" --version=1.4.0 \
                           --description="Fixes for landscape rendering and signup." \
                           --issues=GET-12,GET-15,GET-21
```

**Fields**

- `--title="…"` *(required)* — customer-readable release name
- `--version=<v>` — e.g. `1.4.0`; free-form
- `--description="…"` — release notes; shown in the dashboard
- `--issues=<csv>` — comma-separated issue identifiers (shortcodes or UUIDs)
- `--product=<id>` — override the linked product for this call