What happened
PR conforma/cli#3379 was a Renovate bot-authored security dependency bump that was autoclosed without merge on 2026-07-09T16:05:57Z after being open for 7 days with a known artifact failure from creation. The retro agent was dispatched at 16:07:01 UTC — approximately 1 minute after close (workflow run 29032135778). Sibling PR #3380 was also autoclosed at nearly the same time (16:06:01Z). Both PRs had known artifact failures from creation and were superseded by PR #3378 on main which was merged on Jul 8.
What could go better
While this particular retro did surface novel findings (the artifact failure + approval quality gap), the general pattern of dispatching retros on bot-authored dependency PRs closed without merge is wasteful. These PRs are typically superseded by a newer version or were broken from the start. The closure was predictable given the unresolved artifact failure and the main-branch PR #3378 already being merged. This is the same pattern documented in #3177 with multiple existing evidence issues. Confidence is medium: this specific retro happened to be useful, but the category as a whole has low signal-to-noise ratio.
Proposed change
This is evidence for existing issue #3177 (Skip retro dispatch on bot-authored dependency PRs closed without merge). No new issue needed. The data point strengthens the case: PR authored by renovate[bot], closed without merge after 7 days, had a known artifact failure from creation, and was superseded by a merged PR on main. The retro dispatch could have been skipped by checking: (1) author is a bot, (2) PR was closed without merge, (3) no human engagement beyond the review agent.
Validation criteria
The retro dispatch pipeline should skip PRs matching: bot-authored + closed-without-merge + dependency-only change. After implementing #3177, this PR would not trigger a retro dispatch. Can be measured by counting retro dispatches on autoclosed bot PRs before and after the fix.
Generated by retro agent from conforma/cli#3379
What happened
PR conforma/cli#3379 was a Renovate bot-authored security dependency bump that was autoclosed without merge on 2026-07-09T16:05:57Z after being open for 7 days with a known artifact failure from creation. The retro agent was dispatched at 16:07:01 UTC — approximately 1 minute after close (workflow run 29032135778). Sibling PR #3380 was also autoclosed at nearly the same time (16:06:01Z). Both PRs had known artifact failures from creation and were superseded by PR #3378 on main which was merged on Jul 8.
What could go better
While this particular retro did surface novel findings (the artifact failure + approval quality gap), the general pattern of dispatching retros on bot-authored dependency PRs closed without merge is wasteful. These PRs are typically superseded by a newer version or were broken from the start. The closure was predictable given the unresolved artifact failure and the main-branch PR #3378 already being merged. This is the same pattern documented in #3177 with multiple existing evidence issues. Confidence is medium: this specific retro happened to be useful, but the category as a whole has low signal-to-noise ratio.
Proposed change
This is evidence for existing issue #3177 (Skip retro dispatch on bot-authored dependency PRs closed without merge). No new issue needed. The data point strengthens the case: PR authored by renovate[bot], closed without merge after 7 days, had a known artifact failure from creation, and was superseded by a merged PR on main. The retro dispatch could have been skipped by checking: (1) author is a bot, (2) PR was closed without merge, (3) no human engagement beyond the review agent.
Validation criteria
The retro dispatch pipeline should skip PRs matching: bot-authored + closed-without-merge + dependency-only change. After implementing #3177, this PR would not trigger a retro dispatch. Can be measured by counting retro dispatches on autoclosed bot PRs before and after the fix.
Generated by retro agent from conforma/cli#3379