Skip to content

fix(ci): declare explicit workflow permissions - #26

Merged
Rastrian merged 1 commit into
mainfrom
fix/workflow-permissions
Aug 31, 2026
Merged

Rastrian merged 1 commit into
mainfrom
fix/workflow-permissions

Conversation

@Rastrian

Copy link
Copy Markdown
Owner

Summary

Resolves all actions/missing-workflow-permissions Code Scanning alerts by adding a top-level permissions block (contents: read) to the four workflows that lacked one:

  • .github/workflows/spore.yml
  • .github/workflows/e2e.yml
  • .github/workflows/e2e-interop.yml
  • .github/workflows/soak.yml

Each block is placed right after the on: block. All workflows only check out code, cache deps, and upload artifacts, so contents: read (least privilege) is sufficient — no other permissions were needed anywhere.

Validation

  • All four files pass python3 -c "import yaml; yaml.safe_load(...)" (valid YAML).
  • Diff is limited to the 12 added lines shown above; nothing else changed.

🤖 Generated with Claude Code

Add a top-level permissions block (contents: read) to spore.yml,
e2e.yml, e2e-interop.yml and soak.yml to resolve the
actions/missing-workflow-permissions Code Scanning alerts and follow
the principle of least privilege.

Co-Authored-By: Claude <noreply@anthropic.com>
@Rastrian
Rastrian merged commit 97157fb into main Aug 31, 2026
3 checks passed
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.

1 participant