chore: set up backport rule for 53

[aljo242]

change 52 to 53

Summary by CodeRabbit

• Chores
  • Streamlined the automated patch backporting process to support the new release branch, ensuring that maintenance updates are now directed to the current release cycle.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the backporting rules in the .mergify.yml file. The configuration is adjusted to target the v0.53.x branch instead of the previous v0.52.x branch. The changes include modifying the rule name, label condition, and the backport branch, effectively shifting the automated backport process to the new version.

Changes

File	Change Summary
.mergify.yml	Updated rule name from "backport patches to v0.52.x branch" to "backport patches to v0.53.x branch" Modified label condition from backport/v0.52.x to backport/v0.53.x Changed target branch from release/v0.52.x to release/v0.53.x

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant PR as Pull Request System
    participant Mergify as Mergify Bot

    Dev->>PR: Create PR with label "backport/v0.53.x"
    PR->>Mergify: Notify new PR event
    Mergify->>Mergify: Read updated .mergify.yml configuration
    Mergify->>PR: Initiate backport process to branch "release/v0.53.x"

Loading

Suggested reviewers

• julienrbrt

---

📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 05933ed and 1beafac.

📒 Files selected for processing (1)

• .mergify.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (8)

• GitHub Check: tests (03)
• GitHub Check: tests (02)
• GitHub Check: tests (01)
• GitHub Check: tests (00)
• GitHub Check: build (arm64)
• GitHub Check: build (amd64)
• GitHub Check: dependency-review
• GitHub Check: Summary

🔇 Additional comments (3)

.mergify.yml (3)

15-15: Backport Rule Name Update Validity
The backport rule name has been updated to "backport patches to v0.53.x branch", aligning with the new branch target. This meets the PR objective and correctly distinguishes it from previous version rules.

---

18-18: Label Condition Updated
The label condition has been updated to "label=backport/v0.53.x", ensuring that the backport trigger is associated with the correct version. This change is clear and consistent in its intent.

---

22-22: Target Branch Updated
The backport action now targets the "release/v0.53.x" branch, which is required for the new versioning rule. The update is consistent with the rule name and label changes, ensuring proper routing of backport operations.

---

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

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.