Stamp release and commit onto every reported event
Errors that cannot be attributed to a deploy, stamped with the release and commit that produced them.
The ticket
Attach the release version and commit hash to every reported error event.
Acceptance criteria
- Every event carries a release identifier and a commit hash
- The release is created in the tracker as part of the deploy
- A new error can be attributed to the deploy that introduced it
- The identifier matches what the deploy pipeline uses
What lands as proof
A tracker view filtered by release, showing which errors began with which deploy.
Why teams defer it
- Attribution only matters during a regression, and during a regression nobody stops to add metadata.
- It touches the deploy pipeline, which is usually owned by somebody else.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: attach the release version and commit hash to every reported error event. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means an error attributes to the deploy that introduced it, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.