[Copilot]

The release binaries workflow run name was static, making it difficult to identify which version was being built in the GitHub Actions UI.

Changes

• Updated workflow name to dynamically include the release tag: Release Binaries ${{ github.event.inputs.release-tag }}

When triggering the workflow with release-tag "v1.2.3", the workflow run will now display as "Release Binaries v1.2.3" in the Actions tab instead of the generic "Release desktop binaries".

Original prompt

Update the release binaries workflow to include the version information in the workflow run name. At the top of the workflow file, set:

name: Release Binaries ${{ github.event.inputs.version }}

Do not include 'v' before the version. Only add this syntax exactly. Ensure all workflow logic and triggers remain unchanged except for updating the workflow name.

This pull request was created as a result of the following prompt from Copilot chat.

Update the release binaries workflow to include the version information in the workflow run name. At the top of the workflow file, set:

name: Release Binaries ${{ github.event.inputs.version }}

Do not include 'v' before the version. Only add this syntax exactly. Ensure all workflow logic and triggers remain unchanged except for updating the workflow name.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Phil Nachreiner (philnach)]

John Bowen (@bowencode) / Mark Brown (@markjbrown) this will make it easier to identify the release runs by adding the inputted version information.