Skip to content

Scope create-release workflow token permissions explicitly - #330

Draft
JarryShaw with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-code-scanning-alert-5
Draft

Scope create-release workflow token permissions explicitly#330
JarryShaw with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-code-scanning-alert-5

Conversation

Copilot AI commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

This change addresses the code scanning finding on .github/workflows/create-release.yml by removing reliance on default GITHUB_TOKEN permissions. The release job now declares the minimum repository access it needs to publish a GitHub release.

  • What changed

    • Added an explicit job-level permissions block to the github release job.
    • Scoped the token to contents: write, which is required for softprops/action-gh-release to create/update releases.
  • Why this matters

    • Makes workflow privileges explicit and least-privilege by default.
    • Resolves the actions/missing-workflow-permissions alert on the release workflow.
  • Relevant diff

    github:
      name: GitHub Release
      runs-on: ubuntu-latest
      permissions:
        contents: write

Co-authored-by: JarryShaw <15666417+JarryShaw@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix code scanning alert #5 Scope create-release workflow token permissions explicitly Aug 13, 2026
Copilot AI requested a review from JarryShaw August 13, 2026 04:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants