Cherry-pick #4965: workflow permissions for v2.4.1 release#4975
Merged
kaidaguerre merged 1 commit intov2.4.xfrom Apr 7, 2026
Merged
Cherry-pick #4965: workflow permissions for v2.4.1 release#4975kaidaguerre merged 1 commit intov2.4.xfrom
kaidaguerre merged 1 commit intov2.4.xfrom
Conversation
kaidaguerre
force-pushed
the
fix/workflow-permissions-cherry-pick
branch
from
3e27004 to
24d9275
Compare
cbruno10
approved these changes
Apr 7, 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
2 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.
Cherry-picks the workflow hardening from develop onto v2.4.x so the release workflow can push the v2.4.1 tag. Org-wide default GITHUB_TOKEN was changed to read; this adds explicit permissions: contents: write to the workflows. Required for today's CVE remediation release.