Every driver you ship is a new release, and when something starts going wrong the first thing you usually want to know is which version is doing it. Anvil already captures the driver version on errors and shows which versions are affected for each error group. Release tracking would extend that coverage to events and logs, and layer a proper notion of a release on top — with release notes, status, adoption metrics, and side-by-side comparison.

The Releases page would list every version of a driver with the errors, events, and a quick sense of how each release is performing in the field. When you look at a single release, you'd see the errors that first appeared in that version, a summary of event volume, and an adoption curve showing how many controllers are running it over time. Error detail pages would pick up "Introduced in v1.2.3" and "Fixed in v1.2.4" context so you can tell at a glance which deployment caused or resolved an issue.

Releases can be created manually — with notes you write when you cut a version — or drafted automatically when Anvil sees a previously-unknown version appear in telemetry. Comparison between two releases surfaces the differences that matter: errors present in the new release but not the old one, errors the new release resolved, and shifts in error rate or event volume between the two. Coupled with the existing source-map upload flow, this turns version tags into a first-class dimension you can filter, compare, and correlate against.