Skip to content

Conversation

@picatz
Copy link
Contributor

@picatz picatz commented Oct 29, 2025

Summary

  • .github/workflows/ci.yaml: Set workflow default to contents: read at ci.yaml:29 and added job-level contents/actions read permissions for reusable feature test calls at ci.yaml:190,203,215,227,239,251 to cover artifact downloads.
  • .github/workflows/docker-images.yaml: Added workflow-level contents: read to lock down the default token while preserving checkout access at docker-images.yaml:34.
  • .github/workflows/dotnet.yaml: Declared workflow-level contents: read and actions: read at dotnet.yaml:26 so artifact downloads and repo access work with least privilege.
  • .github/workflows/go.yaml: Declared workflow-level contents: read and actions: read at go.yaml:26 to cover checkout and optional artifact retrieval.
  • .github/workflows/java.yaml: Declared workflow-level contents: read and actions: read at java.yaml:27 for checkout plus artifact download support.
  • .github/workflows/php.yaml: Declared workflow-level contents: read and actions: read at php.yaml:26 to scope the token while allowing artifact access when needed.
  • .github/workflows/python.yaml: Declared workflow-level contents: read and actions: read at python.yaml:26 to cover checkout, protoc setup, and artifact download.
  • .github/workflows/typescript.yaml: Declared workflow-level contents: read and actions: read at typescript.yaml:26 for checkout plus optional artifact usage.
  • .github/workflows/all-docker-images.yaml: Added workflow-level contents: read at all-docker-images.yaml:70 so reusable image-build calls inherit explicit read-only defaults.

This change was made by an automated process to ensure all GitHub Actions workflows have explicitly defined permissions as per best practices.
@Sushisource Sushisource merged commit b620a92 into main Oct 29, 2025
22 of 23 checks passed
@Sushisource Sushisource deleted the security-campaign/set-explicit-github-actions-permissions branch October 29, 2025 18:13
picatz added a commit to temporalio/sdk-python that referenced this pull request Oct 30, 2025
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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants