Add explicit permissions for CI and NOTICE regeneration workflows#472
Merged
rzo1 merged 1 commit intoMay 18, 2026
Merged
Conversation
Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
arpitjain099
force-pushed
the
security/workflow-permissions-ci-and-license-pr
branch
from
808e07e to
c6848b0
Compare
Contributor
Author
|
Hi @mawiesne, gentle ping on this. PR has been open for 4 days without review. I noticed you've been on the recent-merger side of recent merges in this repo. When you have a moment, would you mind giving it a quick look? No urgency. Happy to address any feedback. |
rzo1
approved these changes
May 18, 2026
mawiesne
approved these changes
May 18, 2026
jzonthemtn
approved these changes
May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
permissionsin.github/workflows/maven.ymlwithcontents: read.permissionsin.github/workflows/license.yamlwith only required write scopes:contents: writepull-requests: writeWhy
These workflows currently rely on default token scopes. Declaring permissions explicitly improves least-privilege posture while preserving existing behavior, including automated NOTICE regeneration PRs.