fix: Workflow does not contain permissions

[shenxianpeng]

Potential fix for https://github.com/commit-check/commit-check-action/security/code-scanning/1

To fix the problem, add an explicit permissions: block to the workflow. You should add it at the top level (root) of the workflow (just after the name: or on: block), or if you prefer to give each job specific permissions, to the relevant job(s). The ideal permissions depend on what the workflow does. As a minimal safe starting point, set contents: read. This ensures the GITHUB_TOKEN used by this workflow job has only read-only access to the repository contents, and no unnecessary write privileges.

In .github/workflows/release-drafter.yml, add:

permissions:
  contents: read

between the name: and on: blocks (as per the common convention and GitHub Actions YAML structure).

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

Summary by CodeRabbit

• Chores
  • Updated release automation to run only on the main branch and support manual triggers, providing clearer release control.
  • Restricted workflow permissions to read-only for repository contents to enhance security and compliance.
  • This update impacts internal release tooling only; no user-facing changes.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Updated the GitHub Actions release-drafter workflow: added a top-level permissions block with contents: read, restricted push trigger to the main branch, and enabled manual triggering via workflow_dispatch. No other logic changes.

Changes

Cohort / File(s)	Summary of Changes
Release workflow configuration .github/workflows/release-drafter.yml	Added permissions: contents: read; restricted on: push to branch main; added workflow_dispatch trigger; no other workflow logic modified.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I twitch my ears at YAML’s tune,
A push to main, a manual boon.
Permissions set, neat as a burrow,
Drafts release on the morrow.
Hop, hop—workflow’s light and clean,
Carrots queued for shipping green.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 857cc3c and 570c801.

📒 Files selected for processing (1)

• .github/workflows/release-drafter.yml (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

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

---

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.
  • 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.
• 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 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/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[github-actions]

Commit-Check ✔️