🌿 Fern Regeneration -- August 29, 2025 #31
Conversation
![fern-api[bot]](https://avatars.githubusercontent.com/in/244756?s=60&v=4){kind=small}
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| runs-on: ubuntu-latest | ||
|
|
||
| - name: Set up Node | ||
| uses: actions/setup-node@v4 | ||
| with: | ||
| node-version: '20' | ||
| steps: | ||
| - name: Checkout repo | ||
| uses: actions/checkout@v4 | ||
|
|
||
| - name: Bootstrap | ||
| run: ./scripts/bootstrap | ||
| - name: Set up node | ||
| uses: actions/setup-node@v3 | ||
|
|
||
| - name: Run tests | ||
| run: ./scripts/test | ||
| - name: Compile | ||
| run: yarn && yarn test |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 22 days ago
To fix the issue, we should explicitly set a permissions block at the top level of the workflow file, immediately after the workflow name and before the on key. This ensures that all jobs in the workflow operate under limited permissions, specifically contents: read, which is sufficient for tasks that require only checking out code and running builds/tests. No jobs in this workflow need write access or additional scopes, so restricting the default token's access is safest and follows GitHub's recommendations. Only the workflow YAML file, .github/workflows/ci.yml, needs to be updated by inserting a new permissions block.
| @@ -1,4 +1,6 @@ | ||
| name: ci | ||
| permissions: | ||
| contents: read | ||
|
|
||
| on: [push] | ||
|
|
This PR regenerates code to match the latest API Definition.