-
Notifications
You must be signed in to change notification settings - Fork 2
Add python-sdk generator to fern/generators.yml #271
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
Conversation
runs-on: ubuntu-latest | ||
steps: | ||
- name: Checkout repo | ||
uses: actions/checkout@v3 | ||
|
||
- name: Setup node | ||
uses: actions/setup-node@v4 | ||
|
||
- name: Download Fern | ||
run: npm install -g fern-api | ||
|
||
- name: Release SDKs | ||
env: | ||
FERN_TOKEN: ${{ secrets.FERN_TOKEN }} | ||
FERN_PYPI_TOKEN: ${{ secrets.FERN_PYPI_TOKEN }} | ||
run: | | ||
fern generate --group python-sdk --version ${{ inputs.version }} --log-level debug |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 18 days ago
The best way to fix this issue is to introduce an explicit permissions
block at the root of the workflow file. This block will define minimal permissions required for the workflow to function correctly. Based on the workflow's operations, it likely only requires contents: read
permission for accessing the repository's code. If additional permissions are required (e.g., pull-requests: write
), they can be added accordingly.
To implement the fix:
- Add a
permissions
key at the root level of the workflow file (beforejobs
). - Set the permissions to
contents: read
, as this workflow primarily interacts with the repository's contents.
-
Copy modified lines R3-R5
@@ -1,5 +1,8 @@ | ||
name: Release Python SDK | ||
|
||
permissions: | ||
contents: read | ||
|
||
on: | ||
workflow_dispatch: | ||
inputs: |
No description provided.