Skip to content

chore: Potential fix for code scanning alert no. 312: Workflow does not contain permissions#245

Draft
asatt wants to merge 2 commits into
mainfrom
alert-autofix-312
Draft

chore: Potential fix for code scanning alert no. 312: Workflow does not contain permissions#245
asatt wants to merge 2 commits into
mainfrom
alert-autofix-312

Conversation

@asatt
Copy link
Copy Markdown
Collaborator

@asatt asatt commented Apr 9, 2026

Potential fix for https://github.com/Netcracker/qubership-logging-operator/security/code-scanning/312

Add an explicit permissions block to the upload-assets job in .github/workflows/docker-release.yml.

Best fix without changing intended functionality:

  • In the upload-assets job, define only the scopes needed for checkout + uploading release assets.
  • actions/checkout needs contents: read.
  • Uploading assets to a release typically needs contents: write.
  • Therefore set:
    • contents: write

Where to change:

  • File: .github/workflows/docker-release.yml
  • Region: job upload-assets (around current lines 121–137), directly under runs-on.

No imports/dependencies/methods are needed; this is YAML workflow configuration only.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

…es not contain permissions

Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
@asatt asatt changed the title Potential fix for code scanning alert no. 312: Workflow does not contain permissions chore: Potential fix for code scanning alert no. 312: Workflow does not contain permissions Apr 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

2 participants