Potential fix for code scanning alert no. 3: Workflow does not contain permissions

[aaguiarz]

Potential fix for https://github.com/openfga/python-sdk/security/code-scanning/3

To fix the problem, add an explicit permissions block to the create-release job in .github/workflows/main.yaml. This block should grant only the minimal permissions required for the job to function. Since the job creates a GitHub release, it requires contents: write permission. The block should be added directly under the create-release: job definition, before the steps: key. No other changes are needed.

---

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

Summary by CodeRabbit

• Chores
  • Updated release workflow permissions to ensure proper access for creating releases.

[coderabbitai]

Walkthrough

The create-release job in the GitHub Actions workflow configuration has been updated to include explicit contents: write permissions, allowing the job to write repository contents. No other changes were made to the workflow steps or logic.

Changes

Cohort / File(s)	Change Summary
Workflow Permissions Update .github/workflows/main.yaml	Added permissions: contents: write to the create-release job to explicitly grant write access to repository contents.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch alert-autofix-3

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai generate unit tests to generate unit tests for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.66%. Comparing base (04d05c4) to head (991a9dd).

❌ Your project status has failed because the head coverage (70.66%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files

@@ Coverage Diff @@ ## main #206 +/- ## ======================================= Coverage 70.66% 70.66% ======================================= Files 134 134 Lines 10866 10866 ======================================= Hits 7679 7679 Misses 3187 3187 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/main.yaml (1)

97-99: Principle-of-Least-Privilege looks good; consider a default blanket restriction

Adding permissions: contents: write at job scope resolves the code-scanning alert and is the minimal scope required by the release action.
For extra hardening you could also set a workflow-level default such as

permissions: {}

or, if read access is still needed elsewhere,

permissions: contents: read

and continue to override per-job as done here. This prevents any future job from silently inheriting broader token rights.
No action is strictly required for this PR, but the tweak keeps the workflow aligned with GitHub’s security guidance.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 04d05c4 and 991a9dd.

📒 Files selected for processing (1)

• .github/workflows/main.yaml (1 hunks)