Description
Loop 6 landed the email feature through a reconciled local branch at main 7a7bbdd, but release-please PR #20 at that exact base proposes 0.5.2 and lists only three fixes. Its generated CHANGELOG omits the Email Routing and Sending feature commit a4aeb08 and other conventional commits reachable since v0.5.1. The loop release gate requires the feature and every newly landed fix in the release notes, so CFO-0024 deployment is parked without merging this PR. Determine why the merged history is omitted and correct the release candidate without rewriting published history.
Acceptance Criteria
- #1 The release candidate changelog at a named main SHA lists the Email Routing and Sending feature and each newly delivered fix since v0.5.1, without duplicating patch-equivalent fixes already in v0.5.1.
- #2 The candidate version reflects the feature under the repository release policy, and every required workflow at its base SHA concludes successfully before merge.
- #3 A reproducible check demonstrates that a future merged local branch with conventional commits is represented in the generated release notes.
Definition of Done
- #1 just check (fmt-check, lint, vet, test, tidy-check, build, vuln)
- #2 just ci before a change that touches the Dockerfile, goreleaser or the image (adds snapshot + image)
- #3 Every new signal or attribute name declared in internal/semconv and listed in docs/signals.md
Implementation Notes
Loop 7: release notes checker landed at 50e1561 and alias repair at 198d4dc. PR #20 at base 1daf4be and head a4a8cff proposed 0.6.0, listed the Email Routing/Sending feature and all 15 required conventional subjects; just relnotes-check passed. CI 36237411272 had ci-success success; required latest base workflows passed. PR #20 merged as eb5c2c7; Release 36238560403 succeeded and published v0.6.0. The earlier superseded auto-rc run 36237432752 was skipped and not counted.
Loop 7 run-end: implementation attempts 1/4, review-repair 1/3 for the empty-commit alias checker correction, infrastructure retries 1 CodeRabbit connection failure; grant: release-note checker and bounded metadata restore commits. Done because PR #20 had 15/15 required subjects, base workflows passed and v0.6.0 Release run 36238560403 succeeded.
Final Summary
Restored complete 0.6.0 release notes and added a reproducible coverage check. Verified 15/15 required subjects against the generated PR body, exact-base CI, and the published release.