workflows: Update to send version updating PR on 4.0 with using v4.0 branch

[cosmo0920]

---

Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

• Example configuration file for the change
• Debug log output from testing the change

• Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

• Run local packaging test showing all targets (including any new ones) build.
• Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

• Documentation required for this feature

Backporting

• Backport to latest stable release.

---

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

Summary by CodeRabbit

• Chores
  • Updated the release workflow to better handle releases starting with version "4.1".

[coderabbitai]

Walkthrough

A new conditional step was added to the GitHub Actions workflow for the staging-release-create-version-update-pr job. This step targets releases starting with version "4.1" and checks out the repository at the master branch using actions/checkout@v4. Existing steps and the overall workflow remain unchanged.

Changes

Cohort / File(s)	Change Summary
GitHub Actions Workflow Update .github/workflows/staging-release.yaml	Added a conditional step for "4.1" releases to check out the master branch using actions/checkout@v4. Existing workflow logic is otherwise unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

In the garden of YAML where workflows hop,
A new branch for "4.1" makes the bunnies stop.
With a checkout so swift, to master they leap,
Ensuring releases are tidy and neat.
🐇✨

---

📜 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 4e62817 and 9110b58.

📒 Files selected for processing (1)

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

🔇 Additional comments (2)

.github/workflows/staging-release.yaml (2)

1052-1054: Good: 4.0 PRs now target the 4.0 branch

Adding with: ref: 4.0 ensures the version-bump PR is raised against the 4.0 maintenance branch, matching the PR objective and existing branch naming conventions across the workflow.

---

1055-1057: Confirm 4.1 workflow target

We’ve checked the remote branches and found no 4.1 branch—only master exists. As written, the release step will always check out master. Please confirm whether:

• You intend to manage all 4.1 releases directly on master, or
• You plan to create a 4.1 maintenance branch (in which case the workflow should be updated to with: ref: 4.1).

File: .github/workflows/staging-release.yaml
Lines: 1055–1057

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update--version-updating-pr-defs

---

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

Support

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

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 generate unit tests to generate unit tests 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.