# Releases: what shipped, and whether it made things worse

A new page lists every version your services deployed, with error rate and p95 latency compared against the rest of the service.

2026-09-05 · Services

The new **Releases** page answers two questions after a deploy: what shipped across your services, and did it change anything.

- A swimlane per service shows one dot per version, placed when it first served traffic.
- A table groups releases by commit and compares each version's error rate and p95 latency against the rest of the service in the same window, so a canary is measured against the version still running beside it.
- Each release has its own page with the commit, the service's golden-signal charts (with a toggle for this version versus the others), and the error issues that are new, regressed, or still occurring on it.

Maple identifies a release by commit, read from the `vcs.ref.head.revision` resource attribute. Set it to the commit SHA your service was built from. See [OpenTelemetry conventions](/docs/concepts/otel-conventions).

Releases is rolling out gradually. Once it's on for your organization, it appears in the sidebar under **Monitor**.