ci: add explicit permissions to GitHub Actions workflows #981
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 changes
This PR adds explicit
permissionsblocks to GitHub Actions workflows to comply with the upcoming security change on February 2nd, 2026, when the default GitHub token permission will change from "Read and Write" to "Read repository contents and packages permissions."Changes:
closed-issue-message.ymlaws-actions/closed-issue-messageaction.Without explicit permissions, this workflow will break when the repo default changes to read-only. This follows the principle of least privilege by only granting the permissions the workflow actually needs.
Codegen Paramaters Changed or Added
Issue #, if available
Description of how you validated changes
Checklist
yarn testpassespath) behave differently on windows.type,input,enum,interface,unionand scalar types.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.