fix: explicitly specify tag_name in GitHub Release step

[Copilot]

When the release workflow creates a tag mid-run, the softprops/action-gh-release step can fail to locate it automatically, resulting in a "GitHub Releases requires a tag" error.

Change

• Added tag_name: ${{ steps.package-version.outputs.tag }} to the Create GitHub Release step's with block, explicitly passing the tag output from the earlier package-version step:

- name: Create GitHub Release
  uses: softprops/action-gh-release@v2
  with:
    tag_name: ${{ steps.package-version.outputs.tag }}
    generate_release_notes: true

Original prompt

Update the release workflow to fix the 'GitHub Releases requires a tag' error. Currently, the 'Create GitHub Release' step in .github/workflows/release.yaml can fail when the workflow is triggered by a commit to main and the tag is created within the workflow, because the release step does not explicitly specify which tag to use.

Solution:

• In the 'Create GitHub Release' step, add 'tag_name: ${{ steps.package-version.outputs.tag }}' to the 'with' block.

This ensures the correct tag is referenced regardless of how the workflow was triggered, addressing failures when the tag is not automatically available in the release step context.

This pull request was created from Copilot chat.

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

[mkistler]

Looks good. 👍

[mkistler]

I think I have hit every little glitch imaginable in this workflow. I'm hoping that this finally fixes things.