Fix: release-drafter workflow error

[rohan-pandeyy]

Added explicit permissions for contents and pull-requests in the update-release-drafter workflow to improve security and clarify required access levels.

permissions:
  contents: write
  pull-requests: read

This should resolve the Resource not accessible by integration error when creating a release.

Summary by CodeRabbit

• Chores
  • Updated workflow permissions for the release drafting process to enhance security and clarity.

[coderabbitai]

Walkthrough

The GitHub Actions workflow for the release drafter was updated to explicitly define permissions at both the workflow and job levels. The workflow now specifies read-only access for contents globally, while the main job is granted write access to contents and read access to pull requests.

Changes

File(s)	Change Summary
.github/workflows/update-release-drafter.yml	Explicitly set permissions at workflow (contents: read) and job (contents: write, pull-requests: read) levels

Possibly related PRs

• Add Release Drafter configuration and workflow #457: Introduced the initial Release Drafter configuration and workflow, which this PR directly builds upon by refining permissions.

Suggested labels

CI/CD

Poem

A bunny with a workflow plan,
Tweaked permissions—because it can!
Read for the world, write for the job,
No more secrets for hackers to rob.
With paws on the keys and a twitch of its nose,
CI/CD magic—off it goes! 🐇✨

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8035a05 and 4df68e1.

📒 Files selected for processing (1)

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

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Tauri Tests
• GitHub Check: Backend Tests

🔇 Additional comments (2)

.github/workflows/update-release-drafter.yml (2)

10-12: Explicit, least-privilege default looks good
Setting the workflow-wide token to contents: read lowers the baseline privileges for every job—a solid hardening step.

---

15-17: Confirm that write-scope escalation is allowed for this repository
The job correctly requests contents: write and pull-requests: read, which Release Drafter needs to create or update drafts.
GitHub permits job-level escalation only if repository settings don’t forbid it. Please double-check repo/org settings so this job doesn’t still fail with “Resource not accessible by integration”.

---

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.
  • @coderabbitai modularize this function.
• 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.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

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 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.