Skip to content

Scope GITHUB_TOKEN permissions in create-release conda job - #326

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

Scope GITHUB_TOKEN permissions in create-release conda job#326
JarryShaw with Copilot wants to merge 2 commits into
mainfrom
copilot/fix-code-scanning-alert-9

Conversation

Copilot AI commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

This PR addresses code scanning alert #9 (actions/missing-workflow-permissions) in the release workflow by removing implicit default token scope. It applies explicit least-privilege permissions to the affected job.

  • Alert remediation (.github/workflows/create-release.yml)

    • Added explicit permissions on the conda job.
    • Scoped token access to the minimum required for release asset publishing (contents: write).
  • Behavioral impact

    • No workflow logic/path changes; only token permission scope is made explicit.
conda:
  runs-on: ${{ matrix.os }}
  permissions:
    contents: write

Co-authored-by: JarryShaw <15666417+JarryShaw@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix code scanning alert #9 Scope GITHUB_TOKEN permissions in create-release conda job 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