Update permissions to allow release asset attachment during release deploys#364
Merged
Conversation
dkotter
previously approved these changes
Aug 7, 2025
github-project-automation
Bot
moved this from Code Review
to QA Testing
in Open Source Practice
Member
Author
|
Reduced packages scope to read, waiting on checks to pass before merging in |
github-project-automation
Bot
moved this from QA Testing
to Done
in Open Source Practice
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.
Description of the Change
This pull request makes a small update to the deployment workflow permissions for WordPress.org. The permissions are expanded to allow writing to both contents and packages, which may be necessary for publishing or updating packages during deployment.
How to test the Change
Changelog Entry
Credits
Props @jeffpaul.
Checklist: