Stakeholder feedback: GitHub Releases should show which GitHub issues are included in that release. A release can contain many commits, and commits can reference issues. The release workflow should collect issue numbers referenced by commits included since the previous release tag and publish them in the GitHub Release body.\n\nAcceptance criteria:\n- Release workflow identifies the previous release/tag for the current release tag.\n- Release workflow scans commits included in the release range for GitHub issue references.\n- Release notes include a clear fixed/resolved issue list with issue number, title, and link when issues are found.\n- Release notes explicitly state when no linked issues are found.\n- Existing release asset upload/update behavior remains intact.
Stakeholder feedback: GitHub Releases should show which GitHub issues are included in that release. A release can contain many commits, and commits can reference issues. The release workflow should collect issue numbers referenced by commits included since the previous release tag and publish them in the GitHub Release body.\n\nAcceptance criteria:\n- Release workflow identifies the previous release/tag for the current release tag.\n- Release workflow scans commits included in the release range for GitHub issue references.\n- Release notes include a clear fixed/resolved issue list with issue number, title, and link when issues are found.\n- Release notes explicitly state when no linked issues are found.\n- Existing release asset upload/update behavior remains intact.