Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release/19.x: workflows: Fix permissions for release-sources job (#100750) #102373

Merged
merged 1 commit into from
Aug 10, 2024

Conversation

llvmbot
Copy link
Member

@llvmbot llvmbot commented Aug 7, 2024

Backport 82c2259

Requested by: @tstellar

@llvmbot llvmbot added this to the LLVM 19.X Release milestone Aug 7, 2024
@llvmbot
Copy link
Member Author

llvmbot commented Aug 7, 2024

@tru What do you think about merging this PR to the release branch?

@llvmbot
Copy link
Member Author

llvmbot commented Aug 7, 2024

@llvm/pr-subscribers-github-workflow

Author: None (llvmbot)

Changes

Backport 82c2259

Requested by: @tstellar


Full diff: https://github.com/llvm/llvm-project/pull/102373.diff

1 Files Affected:

  • (modified) .github/workflows/release-tasks.yml (+1)
diff --git a/.github/workflows/release-tasks.yml b/.github/workflows/release-tasks.yml
index 7dd4c306671b74..deacc24f54e077 100644
--- a/.github/workflows/release-tasks.yml
+++ b/.github/workflows/release-tasks.yml
@@ -99,6 +99,7 @@ jobs:
   release-sources:
     name: Package Release Sources
     permissions:
+      contents: read
       id-token: write
       attestations: write
     needs:

For reusable workflows, the called workflow cannot upgrade it's
permissions, and since the default permission is none, we need to
explicitly declare 'contents: read' when calling the release-sources
workflow.

Fixes the error:
The workflow is requesting 'contents: read', but is only allowed
'contents: none'.

(cherry picked from commit 82c2259)
@tru tru merged commit eea8e4d into llvm:release/19.x Aug 10, 2024
4 of 5 checks passed
Copy link

@tstellar (or anyone else). If you would like to add a note about this fix in the release notes (completely optional). Please reply to this comment with a one or two sentence description of the fix. When you are done, please add the release:note label to this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

3 participants