Skip to content

fix: move workflow permissions from job level to workflow level#359

Draft
jmeridth wants to merge 1 commit intomainfrom
fix/workflow-permissions-to-workflow-level
Draft

fix: move workflow permissions from job level to workflow level#359
jmeridth wants to merge 1 commit intomainfrom
fix/workflow-permissions-to-workflow-level

Conversation

@jmeridth
Copy link
Collaborator

@jmeridth jmeridth commented Mar 16, 2026

What

Moves permissions declarations from job level back to workflow level across all workflow files.

Why

Workflow-level permissions sets the maximum token permissions for all jobs. With contents: read at workflow level, job-level contents: write was silently capped, causing Resource not accessible by integration errors (e.g., markPullRequestReadyForReview in mark-ready-when-ready).

Notes

  • Multi-job workflows (e.g., release.yml) now declare the union of all job permissions at workflow level, which is slightly broader per-job but avoids the cap issue
  • Reviewers should verify that no workflow previously had intentionally restricted job-level permissions that differ from other jobs in the same workflow

@jmeridth jmeridth requested a review from zkoppert as a code owner March 16, 2026 16:22
@github-actions github-actions bot added the fix label Mar 16, 2026
Job-level permissions are capped by workflow-level permissions. With
workflow-level set to only `contents: read`, job-level write permissions
were silently capped, breaking actions like markPullRequestReadyForReview.
@jmeridth jmeridth force-pushed the fix/workflow-permissions-to-workflow-level branch from f7aa355 to 5c617cd Compare March 16, 2026 16:23
@jmeridth jmeridth marked this pull request as draft March 16, 2026 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant