Potential fix for code scanning alert no. 2: Workflow does not contain permissions #486
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/IgniteUI/igniteui-theming/security/code-scanning/2
To fix this issue, you should add a
permissionsblock to the workflow (.github/workflows/npm-publish.yml). This block should specify the minimal permissions required for the workflow. For an NPM publish workflow triggered on release creation, it is usually sufficient to setcontents: read, unless you need to create new tags or modify repository contents (which you do not in the shown steps).You should add the following block at the top level of the YAML file, just after the
name:or before/after theon:block; this will apply the permissions to all jobs in the workflow unless overridden.No package changes or additional methods are necessary; the fix is purely in the workflow YAML.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.