fix: Add explicit permissions to visual regression workflow #73
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.
Potential fix for https://github.com/cloudscape-design/chart-components/security/code-scanning/3
To fix the problem, add an explicit
permissionsblock to the workflow file. This block should specify the minimal permissions required for each job. For example:testjob, it likely only requirescontents: readsince it primarily checks out the repository, installs dependencies, runs tests, and downloads/upload artifacts.updatejob, it may needcontents: writeto update snapshots.The
permissionsblock should be added at the job level to ensure different permissions fortestandupdatejobs. This ensures each job only has access to what it needs.Suggested fixes powered by Copilot Autofix. Review carefully before merging.