build: bump to v4.2.0

[edsiper]

GIT master is now 4.2.0 (development), a new branch 4.2 has been created. More details in the roadmap link:

https://github.com/fluent/fluent-bit/wiki/Fluent-Bit-Roadmap#release-timing-note-updated-on-oct-2025

---

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
  • Bumped project version to 4.2.0 across build and deployment configuration files.

[chatgpt-codex-connector]

💡 Codex Review

fluent-bit/dockerfiles/Dockerfile

Line 16 in 42e7501

ARG RELEASE_VERSION=4.1.2

Align Docker release version with 4.2.0 bump

The commit sets the project version to 4.2.0 everywhere else, but dockerfiles/Dockerfile still defines ARG RELEASE_VERSION=4.1.2. Anyone building or publishing the Docker image after this change will continue producing a 4.1.2 image even though the rest of the build is 4.2.0, leading to inconsistent artifacts. This argument should be updated to 4.2.0 so the container matches the new release.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting

• @codex fix this CI failure
• @codex address that feedback

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Version bump from 4.1.2 to 4.2.0 applied consistently across build configuration and deployment manifest files, updating version identifiers in CMakeLists.txt, BitBake recipe, and Snapcraft configuration.

Changes

Cohort / File(s)	Summary
Build configuration files CMakeLists.txt, fluent-bit-4.2.0.bb	Version components updated from 4.1.2 to 4.2.0 (FLB_VERSION_MINOR: 1→2, FLB_VERSION_PATCH: 2→0 in CMakeLists.txt; PV: 4.1.2→4.2.0 in BitBake recipe)
Deployment manifests snap/snapcraft.yaml	Snapcraft version property updated from 4.1.2 to 4.2.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Hop, hop, hooray! The version has grown,
From 4.1.2 to 4.2.0—the seeds are sown!
CMake, BitBake, Snapcraft aligned,
A bumpy-bump patch of the most orderly kind! 🌱✨

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch branching-4.2

---

📜 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 d3be337 and 42e7501.

📒 Files selected for processing (3)

• CMakeLists.txt (1 hunks)
• fluent-bit-4.2.0.bb (1 hunks)
• snap/snapcraft.yaml (1 hunks)

---

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 and usage tips.}

[patrick-stephens]

@cosmo0920 @edsiper we need to update the CI to handle this so 4.1/4.0 releases are correctly triggered and managed - particularly for docs/release generation. The security page is also wildly out of date for what versions are supported so that needs an update too.

I will not have time to do this next week due to KCD UK so it likely needs doing asap if you want to release 4.0 or 4.1.