Add actions-read permission to CI workflow #556
Conversation
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
picatz
added a commit
to temporalio/sdk-python
that referenced
this pull request
Oct 30, 2025
Following the same fix done here: temporalio/sdk-dotnet#556 After this was landed: temporalio/features#693
tconley1428
pushed a commit
to temporalio/sdk-python
that referenced
this pull request
Oct 30, 2025
* Set explicit permissions for GitHub Actions workflows This change was made by an automated process to ensure all GitHub Actions workflows have explicitly defined permissions as per best practices. * Add `actions: read` to use `temporalio/features` Following the same fix done here: temporalio/sdk-dotnet#556 After this was landed: temporalio/features#693
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What was changed
In temporalio/features#693, an
action: readpermission is required that is not present here on the caller of features workflows, so it is needed here too.