ci: improve release workflow with PR creation

[EvanNotFound]

• Replace direct push to main with PR creation for new releases
• Update dev branch with new release changes
• Use GitHub CLI to automate PR creation process
• Enhance version control and review process for releases

Summary by CodeRabbit

• New Features

  • Improved release process by introducing a pull request mechanism for merging changes.

• Bug Fixes

  • Enhanced workflow structure for better code review practices.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The pull request introduces significant changes to the GitHub Actions workflow defined in .github/workflows/release.yml. The workflow now includes a new step to create a pull request instead of directly pushing changes. This involves creating a new branch named release/v{VERSION} based on the version from package.json, which is then merged into the dev branch rather than main. These modifications aim to enhance the release process by incorporating a structured pull request mechanism.

Changes

File Path	Change Summary
.github/workflows/release.yml	Replaced Push changes step with Create Pull Request step; added GITHUB_TOKEN setup; created release/v{VERSION} branch; modified Update dev branch step to merge from the new release branch instead of main.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant GitHub
    participant DevBranch
    participant ReleaseBranch

    User->>GitHub: Trigger release workflow
    GitHub->>GitHub: Create release branch (release/v{VERSION})
    GitHub->>GitHub: Push release branch to origin
    GitHub->>GitHub: Create pull request targeting main
    GitHub->>DevBranch: Merge release branch into dev
    DevBranch-->>GitHub: Update dev branch with changes

Loading

Warning

Rate limit exceeded

@EvanNotFound has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 20 minutes and 29 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 2f94a92 and cdecc01.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2f94a92 and cdecc01.

📒 Files selected for processing (1)

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

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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

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.