fix(release): generate cumulative stable notes - #27
Conversation
select prerelease baselines from the latest tag and stable baselines from the previous stable release. refresh release tags and fall back to the first prerelease changelog baseline for initial stable promotion.
ignore local-only and remotely deleted tags when selecting release note baselines. add regression coverage for both cases.
morgmart
left a comment
morgmart
left a comment
There was a problem hiding this comment.
🤖 Automated code review
REQUEST_CHANGES: the stable-note flow can select an unpushed local stable tag, and generated notes can be approved against a stale main snapshot, so a published release may omit shipped changes from its changelog. Static review covered all three changed files and the full exact three-dot comparison. The final self-check covered every changed release flow, consent, accessibility and i18n applicability, lifecycle/race/error behavior, test honesty, project rules, duplicates, and severity evidence; no other supported findings remained. Supplied GitHub evidence was structurally valid and inspected: seven checks were successful and Frontend checks and unit tests was still in progress at capture time; required checks still govern merge readiness.
Deterministic publication result: 2 blocking and 0 non-blocking finding(s) publishable; 0 duplicate(s) suppressed.
recheck the reviewed main cutoff after approval. fast-forward main, regenerate release notes, and require fresh approval when the cutoff changes.
fetch published tags into an isolated pruned namespace and regenerate approved notes when the selected baseline changes. preserve public tag names in comparison links.
2 participants
summary
validation