> ## Documentation Index
> Fetch the complete documentation index at: https://docs.logbrew.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Releases

> Release tracking in LogBrew assigns every log, trace span, issue, and action to a code version and environment.

Every telemetry envelope in LogBrew must include a non-empty `release` and
`environment`. A release is the code version that emitted telemetry, such as
`api@1.2.3`, `ios@2026.06.01`, or a git SHA.

Release tracking makes production questions precise:

* What changed in this version?
* Which issues first appeared after deploy?
* Did action failures increase in production?
* Which traces and logs belong to the same release?

## Release summary

LogBrew keeps an append-friendly release summary with counts for each stream.

| Count              | Meaning                                         |
| ------------------ | ----------------------------------------------- |
| `issue_count`      | Issue events assigned to the release.           |
| `log_count`        | Logs assigned to the release.                   |
| `trace_span_count` | Trace spans assigned to the release.            |
| `action_count`     | Actions assigned to the release.                |
| `first_seen_at`    | First telemetry observed for the release.       |
| `last_seen_at`     | Most recent telemetry observed for the release. |

```bash theme={null}
logbrew read releases --environment production --json
```

## Naming releases

Use a release name that a human and an agent can map back to code.

<CardGroup cols={2}>
  <Card title="Good" icon="check">
    `api@1.2.3`, `web@b7f4d91`, `ios@2026.06.01`, `worker@2026-06-01.1`
  </Card>

  <Card title="Avoid" icon="x">
    `latest`, `prod`, `new`, `build`, empty strings, or values that change
    meaning after deploy.
  </Card>
</CardGroup>

## Environment filters

Use `environment` to separate production from staging or local development.
Release names can repeat across environments.

```bash theme={null}
logbrew read issues --release api@1.2.3 --environment production --json
logbrew read logs --release api@1.2.3 --environment staging --json
```

<Tip>
  Keep release and environment on every SDK envelope. It is cheaper than trying
  to reconstruct deploy context after an incident.
</Tip>