Skip to content

release: update to v4.2.3#2382

Merged
eschabell merged 1 commit intomasterfrom
create-pull-request/patch
Feb 23, 2026
Merged

release: update to v4.2.3#2382
eschabell merged 1 commit intomasterfrom
create-pull-request/patch

Conversation

@fluent-bot
Copy link
Contributor

@fluent-bot fluent-bot commented Feb 18, 2026

Update release 4.2.3 version.

Summary by CodeRabbit

  • Documentation
    • Added Docker image tags for version 4.2.3, including debug and release variants supporting amd64, arm64, and arm/v7 architectures.
    • Updated Windows installation documentation with latest version downloads, checksums, and installation examples for EXE, ZIP, and ARM64 installer variants.

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 18, 2026

📝 Walkthrough

Walkthrough

Documentation updates for Fluent Bit version 4.2.3 across Docker and Windows installation guides. Docker tags added for debug and release images. Windows installer versions, checksums, and URLs updated from 4.2.2 to 4.2.3.

Changes

Cohort / File(s) Summary
Version 4.2.3 Release Documentation
installation/downloads/docker.md, installation/downloads/windows.md
Added Docker tag rows (4.2.3-debug, 4.2.3) and bumped Windows installer documentation from 4.2.2 to 4.2.3, including updated SHA256 checksums, download URLs, and example commands across 32/64-bit EXE, ZIP, and ARM64 variants.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • eschabell
  • patrick-stephens

Poem

🐰 A new release hops into view,
4.2.3 shiny and true!
Checksums dance, URLs align,
Docker and Windows both shine—
Documentation fresh, version divine! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'release: update to v4.2.3' accurately reflects the main change—updating documentation to version 4.2.3 across Docker and Windows installation files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch create-pull-request/patch

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@installation/downloads/docker.md`:
- Line 46: The table row referencing release v4.2.3 contains a broken
announcement link and should be removed or deferred; find the table row that
contains the version string "4.2.3" (the line with "v4.2.3" and the announcement
URL) and either delete that entire row or comment it out/replace it with a
placeholder until the announcement page at
https://fluentbit.io/announcements/v4.2.3/ is published, ensuring the release
table only contains valid links.

In `@installation/downloads/windows.md`:
- Line 131: Update the sentence containing the phrase "These are now using the
Github Actions built versions." to correct branding and hyphenation by replacing
"Github" with "GitHub" and changing "Actions built" to the compound modifier
"Actions-built" so the phrase becomes "These are now using the GitHub
Actions-built versions."; ensure the rest of the sentence ("Legacy AppVeyor
builds are still available (AMD 32/64 only) at releases.fluentbit.io but are
deprecated.") remains unchanged.


<!-- vale on -->

These are now using the Github Actions built versions. Legacy AppVeyor builds are still available (AMD 32/64 only) at releases.fluentbit.io but are deprecated.
Copy link
Contributor

@coderabbitai coderabbitai bot Feb 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix capitalization and hyphenation: "Github Actions built" → "GitHub Actions-built".

"Github" should be "GitHub" (official brand capitalization), and "Actions built" used as a compound modifier before a noun needs a hyphen.

✏️ Proposed fix
-These are now using the Github Actions built versions. Legacy AppVeyor builds are still available (AMD 32/64 only) at releases.fluentbit.io but are deprecated.
+These are now using the GitHub Actions-built versions. Legacy AppVeyor builds are still available (AMD 32/64 only) at releases.fluentbit.io but are deprecated.
🧰 Tools
🪛 LanguageTool

[grammar] ~131-~131: Use a hyphen to join words.
Context: ... These are now using the Github Actions built versions. Legacy AppVeyor builds a...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@installation/downloads/windows.md` at line 131, Update the sentence
containing the phrase "These are now using the Github Actions built versions."
to correct branding and hyphenation by replacing "Github" with "GitHub" and
changing "Actions built" to the compound modifier "Actions-built" so the phrase
becomes "These are now using the GitHub Actions-built versions."; ensure the
rest of the sentence ("Legacy AppVeyor builds are still available (AMD 32/64
only) at releases.fluentbit.io but are deprecated.") remains unchanged.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cosmo0920 this spelling needs to be fixed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!

@eschabell eschabell self-assigned this Feb 18, 2026
@eschabell eschabell added waiting-on-code-merge waiting-on-review Waiting on a review from mainteners 4.2.3 labels Feb 18, 2026
@cosmo0920
Copy link
Contributor

Fluent Bit v4.2.3 is already shipped. :shipit:!

Copy link
Collaborator

@eschabell eschabell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cosmo0920 left comments for two things that need to be addressed, see what you think?


<!-- vale on -->

These are now using the Github Actions built versions. Legacy AppVeyor builds are still available (AMD 32/64 only) at releases.fluentbit.io but are deprecated.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cosmo0920 this spelling needs to be fixed.

@eschabell
Copy link
Collaborator

@cosmo0920 I just noticed that the announcement blog is in the website repo, but not posting under announcements... i will fix that website issue fluent/fluent-bit-website-hugo#131 and then merge this PR here.

Copy link
Collaborator

@eschabell eschabell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The blog article is there, just a website redeploy needed to publish it, ask for that is with @edsiper, so approving this docs update.

@eschabell eschabell merged commit 4a18664 into master Feb 23, 2026
8 checks passed
@eschabell eschabell deleted the create-pull-request/patch branch February 23, 2026 09:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants