Documentation
Release
A release string tags every error from that build so you can compare versions.
What it is
Optional version label on events. Prefer the version already in your package —
package.json (JS), importlib.metadata.version (Python), or JAR
Implementation-Version (Java). Pair with environment so production and
staging stay separate when the version matches.
Also feeds the release incident rule (clusters of new issues after a ship).
In the dashboard
With release set, errors group by version on Releases:
Releases
Latest release
Active now
New issues
3
First seen in this release
Open issues vs previous
−2
vs 1.4.1 (5 open)
| Release | Events | Issues | New |
|---|---|---|---|
| 1.4.1 | 842 | 12 | 1 |
| 1.4.0 | 1.2k | 9 | 0 |
Sample data — your versions and counts come from real errors.
Latest version: new issues first seen after that deploy, and open-issue change vs the previous ship. Below: earlier versions with event and issue counts. On a single issue you still see which version the user was on.
Without a release label, issues and alerts work; you just lose the version breakdown.
In the SDK
Pass release once in init. Take the value from package metadata —
package.json (JS), importlib.metadata.version (Python), or JAR
Implementation-Version (Java). API:
SDK → Release.