release: update to v4.2.0

[fluent-bot]

Update release 4.2.0 version.

• Created by https://github.com/fluent/fluent-bit/actions/runs/19281730660
• Auto-generated by create-pull-request: https://github.com/peter-evans/create-pull-request

Summary by CodeRabbit

• Documentation
  • Updated installation documentation to include version 4.2.0 availability for Docker (x86_64, arm64v8, arm32v7, s390x architectures) and Windows platforms.
  • Added corresponding debug variant documentation for version 4.2.0.

[coderabbitai]

Walkthrough

Documentation updates to reflect version 4.2.0 release across Docker and Windows installation guides. Docker tags table expanded with new 4.2.0 and 4.2.0-debug entries. Windows installation guide updated with 4.2.0 package references, checksums, and download links replacing 4.0.13.

Changes

Cohort / File(s)	Summary
Installation Documentation installation/downloads/docker.md	Added Docker tag entries for version 4.2.0 and 4.2.0-debug with multi-architecture support (x86_64, arm64v8, arm32v7, s390x), positioned before existing 4.0.13 entries
Windows Installation Guide installation/downloads/windows.md	Updated all Windows package references from 4.0.13 to 4.2.0, including installer filenames, SHA256 checksums, MSI names, archive sources, and download links for win32, win64, and winarm64 variants

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify SHA256 checksums are accurate for the 4.2.0 Windows packages
• Confirm the v4.2.0 Docker release link and registry URLs are correct
• Ensure all archive source URLs (win32/win64/winarm64) and MSI links resolve correctly

Poem

🐰 Version hops from old to new, four-point-two in every view!
Docker tags and Windows dressed, installation put to test,
Checksums checked and links so true, this rabbit cheers the upgrade through! ✨

Pre-merge checks and finishing touches

✅ 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.0' directly matches the PR's main objective of updating documentation to version 4.2.0, clearly summarizing the primary change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ 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

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b6f318c and 62642ab.

📒 Files selected for processing (2)

• installation/downloads/docker.md (1 hunks)
• installation/downloads/windows.md (2 hunks)

🧰 Additional context used

🪛 LanguageTool

installation/downloads/windows.md

[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)

🔇 Additional comments (5)

installation/downloads/windows.md (4)

116-116: LGTM — Version statement updated correctly.

The latest stable version line is properly updated to reflect v4.2.0.

---

135-137: LGTM — MSI installer links updated.

All three MSI installer variants (win32, win64, winarm64) are consistently updated to v4.2.0 URLs.

---

142-142: LGTM — Example commands updated.

The Get-FileHash and Expand-Archive PowerShell command examples are correctly updated to reference v4.2.0 filenames.

Also applies to: 152-152

---

122-127: All Windows installer URLs are accessible and checksums are properly formatted.

The package links for all three architectures (win32, win64, winarm64) returned HTTP 200 status codes, confirming they are accessible and working. The checksums are all valid 64-character hexadecimal strings, matching the expected SHA-256 format.

installation/downloads/docker.md (1)

45-46: I need to gather more information about the correct Fluent Bit announcement URL pattern and verify what links exist elsewhere in the documentation.

Now let me check the actual documentation file to see the context and other version entries:

Based on my verification, v4.1.1 is the latest released version (October 09, 2025), and v4.2.0 does not yet exist. The 404 errors are expected—the URL pattern itself is correct and matches existing release announcements like v4.0.10 and v4.0.12. The documentation appropriately includes links to future release announcements in advance of their publication.

LGTM — Docker tags for v4.2.0 added correctly.

Both debug (4.2.0-debug) and release (4.2.0) tags are documented with the correct architecture list (x86_64, arm64v8, arm32v7, s390x) and consistent table formatting. The release link follows the standard announcement URL pattern and will be accessible upon v4.2.0 release.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix capitalization: "GitHub" and clarify hyphenation.

The text "Github Actions built versions" has two issues: "Github" should be capitalized as "GitHub", and "built versions" may be clearer as "Actions-built versions" for consistency with documentation style.

Apply this diff to fix the capitalization and hyphenation:

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

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	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

installation/downloads/windows.md around line 131: fix capitalization and
hyphenation in the sentence by changing "Github Actions built versions" to
"GitHub Actions-built versions" (preserve rest of sentence), so "GitHub" is
correctly capitalized and "Actions-built" is hyphenated for clarity and
consistency.