Use workflow token for releases

[tidy-dev]

Summary

• grant the release job copilot-requests: write
• authenticate Copilot CLI with the built-in ${{ github.token }}
• remove the nonexistent COPILOT_GITHUB_TOKEN secret dependency
• publish releases immediately by default, with an optional draft workflow input

Validation

• parsed and inspected the workflow authentication and release configuration
• verified the published v1 action supports falling back to GITHUB_TOKEN
• verified version calculations produce v1.0.3, v1.1.0, and v2.0.0 from v1.0.2
• verified the boolean draft input defaults to false and controls release creation
• PR end-to-end CI exercises Copilot authentication with the same workflow-token permission

The release workflow has never run, so creating a release and moving tags cannot be fully exercised without performing a real release.

[Copilot]

Pull request overview

Updates release authentication to use the built-in workflow token.

Changes:

• Grants copilot-requests: write.
• Removes the custom token secret dependency.
• Changes releases from draft to immediately published.

Show a summary per file

File	Description
.github/workflows/release.yml	Updates release permissions, authentication, and publication behavior.

Review details

Tip

Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Balanced