fix(ci): added permission for id-token to git-pr-release.

[hwakabh]

Issue/PR link

relates: #564

What does this PR do?

Describe what changes you make in your branch:

• added id-token: write permissions for git-pr-release

(Optional) Additional Contexts

Describe additional information for reviewers (i.e. What does not included)

• e2e testings are not included in this PR, since this requires merge into main to confirm changes would be applied

Summary by CodeRabbit

• Chores
  • Enhanced the automation process to support secure, token-based authentication during releases.

[coderabbitai]

Walkthrough

This pull request updates the GitHub Actions workflow configuration by introducing a new permission setting. Specifically, the id-token permission is added with a value of write, allowing the workflow to generate and utilize an ID token for authentication purposes. The existing permissions for contents (read) and pull-requests (write) remain unchanged.

Changes

File	Change Summary
.github/workflows/git-pr-release.yaml	Added id-token: write permission to enable generation and use of an ID token; existing permissions for contents and pull-requests are retained.

Possibly related PRs

• security: added workflow permissions. #564: Involves modifications to workflow file permissions to enhance security, similar to the updates introduced in this PR.

Suggested labels

ci, deploy

---

📜 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 3cf7519 and 522ad95.

📒 Files selected for processing (1)

• .github/workflows/git-pr-release.yaml (1 hunks)

🔇 Additional comments (1)

.github/workflows/git-pr-release.yaml (1)

9-13: Explicit Permission Grant for id-token: write Added

The new permission for id-token: write is correctly added to the permissions block, enabling the workflow to generate and utilize an ID token as required by the git-pr-release job. This change appropriately complements the existing permissions for contents (read) and pull-requests (write). Please ensure that downstream steps that rely on the ID token are secured and behave as expected during actual release operations.

---

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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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