-
Notifications
You must be signed in to change notification settings - Fork 15
release v1.3.2 #90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release v1.3.2 #90
Conversation
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Co-authored-by: Renovate Bot <bot@renovateapp.com>
| runs-on: ubuntu-latest | ||
| steps: | ||
| - name: Checkout | ||
| uses: actions/checkout@v4.2.2 | ||
| - name: Self-hosted Renovate | ||
| uses: renovatebot/github-action@v42.0.0 | ||
| with: | ||
| configurationFile: .github/configs/renovate-config.js | ||
| token: ${{ secrets.RENOVATE_PAT_TOKEN }} | ||
| env: | ||
| LOG_LEVEL: debug |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 9 months ago
To fix the issue, add a permissions block to the workflow. Since the workflow primarily checks out the repository and uses Renovate for dependency updates, it likely only requires contents: read permissions. This ensures that the GITHUB_TOKEN is restricted to read-only access, adhering to the principle of least privilege.
The permissions block should be added at the root level of the workflow to apply to all jobs. If specific jobs require additional permissions, they can override the root-level permissions.
-
Copy modified lines R7-R8
| @@ -6,2 +6,4 @@ | ||
| workflow_dispatch: | ||
| permissions: | ||
| contents: read | ||
| jobs: |
No description provided.