ci: Harden workflows with least-privilege permissions and per-PR concurrency#517
Merged
Conversation
…urrency Add an explicit top-level `permissions: contents: read` block to both workflows so the GITHUB_TOKEN no longer inherits the repo/org default (potentially read-write). Neither workflow need github write level permissions, image pushed are authenticated to quay.io, all that's needed from github is read-only to checkout the source. Add a per-PR concurrency group that cancels superseded in-progress runs. The group is keyed on github.ref so each PR (and main) is isolated, and cancel-in-progress is gated on `event_name == 'pull_request'` so push-to-main release builds always run to completion. Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
viktor-kurchenko
approved these changes
Jul 2, 2026
aanm
approved these changes
Jul 2, 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
3 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.
Add an explicit top-level
permissions: contents: readblock to both workflows so the GITHUB_TOKEN no longer inherits the repo/org default (potentially read-write). Neither workflow need github write level permissions, image pushed are authenticated to quay.io, all that's needed from github is read-only to checkout the source.Add a per-PR concurrency group that cancels superseded in-progress runs. The group is keyed on github.ref so each PR (and main) is isolated, and cancel-in-progress is gated on
event_name == 'pull_request'so push-to-main release builds always run to completion.