ci: limit permission scope on lambda layer github action #1555
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
CodeQL flagged a missing permissions block on the validate job in the Lambda layer publish workflow.
Without explicit permissions, the job inherits the default repository GITHUB_TOKEN permissions, which
violates the principle of least privilege.
The validate job only runs a bash string comparison to confirm user intent—it doesn't interact with
GitHub APIs or access repository contents. Explicitly setting empty permissions ensures this job has no
unnecessary access, consistent with how other workflows in this repository are configured.
Resolves: https://github.com/strands-agents/sdk-python/security/code-scanning/8
Related Issues
#636
Documentation PR
N/A
Type of Change
Bug fix
Testing
How have you tested the change? Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli
hatch run prepareChecklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.