release: update to v4.2.2

[fluent-bot]

Update release 4.2.2 version.

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

Summary by CodeRabbit

• Documentation
  • Added Docker container image tags for version 4.2.2, including standard and debug variants with multi-architecture support.
  • Updated Windows installation documentation with version 4.2.2 download links and verification checksums.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation updates for Fluent Bit version 4.2.2 across installation guides: Docker registry now includes two new tagged entries (4.2.2-debug and 4.2.2), while Windows installation references have been bumped from 4.2.1 to 4.2.2 with updated checksums and artifact links.

Changes

Cohort / File(s)	Summary
Docker Release Tags installation/downloads/docker.md	Added two new entries to the Tags table for version 4.2.2: 4.2.2-debug and 4.2.2, each with multi-architecture support descriptions
Windows Installation References installation/downloads/windows.md	Updated all 4.2.1 references to 4.2.2, including: latest version identifier, EXE/ZIP/MSI installer URLs, SHA256 checksums, and verification commands (Get-FileHash, Expand-Archive parameters)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• fluent/fluent-bit-docs#2300 — Updates the same files for a prior version bump (4.2.1 to 4.2.2), establishing the release documentation pattern
• fluent/fluent-bit-docs#2169 — Similar version release updates across installation guides for a different patch version (4.2.0)

Suggested reviewers

• esmerel
• cosmo0920
• eschabell

Poem

🐰 A new version hops into the guides so bright,
Docker tags and Windows paths now polished right,
From 4.2.1 to 4.2.2 we leap with cheer,
Release notes updated—documentation's clear! 🎉

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.2' accurately reflects the main change: updating documentation to version 4.2.2 across Docker and Windows installation files.
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: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7fb7ce2 and 79ce743.

📒 Files selected for processing (2)

• installation/downloads/docker.md
• installation/downloads/windows.md

🧰 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 (2)

installation/downloads/docker.md (1)

45-46: Docker registry entries correctly formatted and positioned.

The new 4.2.2-debug and 4.2.2 tags are properly added to the top of the table with matching architecture support (x86_64, arm64v8, arm32v7, s390x) and descriptions consistent with existing release entries. The release announcement link follows the established convention.

installation/downloads/windows.md (1)

116-116: Version updates consistently applied across Windows installation guides.

All references to 4.2.2 are properly updated: version statement, installer download links, MSI entries, and command examples. Checksums are in the expected SHA256 format, and artifact URLs follow the established pattern.

Also applies to: 122-127, 135-137, 142-142, 152-152

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix hyphenation in compound adjective.

Line 131 uses "Github Actions" as a compound adjective; it should be hyphenated as "Github-Actions" for grammatical correctness.

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

📝 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

In installation/downloads/windows.md around line 131, the phrase "Github Actions
built versions" should use a hyphenated compound adjective; change it to
"Github-Actions built versions" (or "GitHub-Actions" if you prefer correct
product capitalization) so the modifier properly hyphenates the compound
adjective before "built versions."