github: workflows: Update release workflow for 5.1 development cycle

[cosmo0920]

Without this patch, we won't update the latest release as 5.1.0 on releasing v5.1.0.

---

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 staging releases to use the latest 5.1 container tags.
  • Preserved separate release handling for version 5.0 and the latest 5.1 release.
  • Improved automated documentation and version-update steps during releases.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 70f8d36b-0a03-4232-b7bb-61f35c821a1f

📥 Commits

Reviewing files that changed from the base of the PR and between cbe1253 and 36702c8.

📒 Files selected for processing (1)

• .github/workflows/staging-release.yaml

---

📝 Walkthrough

Walkthrough

The staging release workflow now treats 5.0 releases as non-latest and 5.1 releases as latest. It updates container tags, release creation, documentation checkout, and version-update checkout paths accordingly.

Changes

Staging release routing

Layer / File(s)	Summary
Version-specific staging release paths .github/workflows/staging-release.yaml	The workflow routes latest container tags and release steps to 5.1, while 5.0 uses non-latest release handling. Documentation and version-update checkouts now use dedicated 5.0 and 5.1 paths.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• fluent/fluent-bit#11631: Both changes update staging release handling for 5.x branches in the same workflow.

Suggested labels: ci

Suggested reviewers: celalettin1286, niedbalski

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the release workflow update for the Fluent Bit 5.1 development cycle.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update-release-process-to-5.1

---

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

_{Comment @coderabbitai help to get the list of available commands.}