Skip to content

chore: update EOL and open changes - #288

Open
jcantrill wants to merge 1 commit into
ViaQ:rh-mainfrom
jcantrill:udpate_readme
Open

chore: update EOL and open changes#288
jcantrill wants to merge 1 commit into
ViaQ:rh-mainfrom
jcantrill:udpate_readme

Conversation

@jcantrill

Copy link
Copy Markdown
Member

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Documentation
    • Updated the release table with Vector 0.54 and RH 6.6.
    • Marked RH 6.4 as end-of-life.
    • Added release notes covering multiline line limits, secret-key path separators, event truncation, Prometheus SAR authentication, UDP recovery, and AWS sink metrics.

Walkthrough

The README release table now includes RH 6.6 and marks RH 6.4 as EOL. The patch list now contains six entries for recent fixes and metrics changes.

Changes

README updates

Layer / File(s) Summary
Release status table
README.md
The release table adds the RH 6.6 row and changes RH 6.4 from Current to EOL.
Patch records
README.md
The patch list adds six entries covering multiline line limits, secret-key paths, event truncation, Prometheus SAR authentication, UDP recovery, and AWS sink metrics.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The description only mentions reviewers and does not describe the README changes. Add a brief summary of the EOL update and the documented open or pending changes.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the README updates for EOL status and open changes.
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

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.

@openshift-ci
openshift-ci Bot requested review from Clee2691 and vparfonov August 6, 2026 16:02
@openshift-ci

openshift-ci Bot commented Aug 6, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcantrill

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved label Aug 6, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 37: Add one blank line after the final patch-table row and before the “##
Issues” heading in the README, leaving the table content unchanged.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5313e850-7907-46db-83da-3245d33f9218

📥 Commits

Reviewing files that changed from the base of the PR and between 83ac4a5 and 51c130d.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
| | [Add truncate option for oversized events](https://github.com/vectordotdev/vector/pull/25567) | v0.54-rh | [Pending](https://github.com/vectordotdev/vector/pull/25567) |
| LOG-9375 | [Enhance the prometheus exporter with SAR auth strategy](https://github.com/ViaQ/vector/pull/265) | v0.54-rh | [Pending](https://github.com/vectordotdev/vector/pull/25412) |
| LOG-9560 | [Fix regression for UDP socket recovery after error](https://github.com/ViaQ/vector/pull/281) | v0.54-rh | [Pending](https://github.com/vectordotdev/vector/pull/25844) |
| | [Fix AWS sinks to emit component_sent_bytes_total with component labels](https://github.com/ViaQ/vector/pull/285) | v0.54-rh | [Pending](https://github.com/vectordotdev/vector/pull/25915) |

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Add a blank line after the patch table.

## Issues follows the final table row without a blank line. Add one blank line after Line 37 to resolve markdownlint MD058.

As per path instructions, “Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity”; this comment is limited to the reported lint failure.

🧰 Tools
🪛 markdownlint-cli2 (0.23.2)

[warning] 37-37: Tables should be surrounded by blank lines

(MD058, blanks-around-tables)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 37, Add one blank line after the final patch-table row and
before the “## Issues” heading in the README, leaving the table content
unchanged.

Sources: Path instructions, Linters/SAST tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant