Skip to content

[AUTO] Add release notes for 2.19.6#6249

Merged
peterzhuamazon merged 3 commits into
opensearch-project:2.19from
opensearch-ci-bot:release-chores/release-notes-2.19.6
Jun 26, 2026
Merged

[AUTO] Add release notes for 2.19.6#6249
peterzhuamazon merged 3 commits into
opensearch-project:2.19from
opensearch-ci-bot:release-chores/release-notes-2.19.6

Conversation

@opensearch-ci-bot

Copy link
Copy Markdown
Contributor

Add release notes for 2.19.6

Borderline Calls

  • update kafka to 3.9.2 #6089: Placed in Maintenance — could also be Bug Fixes since it resolves CVEs, but dependency version updates are more consistent with Maintenance categorization.

Signed-off-by: opensearch-ci-bot <opensearch-infra@amazon.com>
@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

PR Reviewer Guide 🔍

(Review updated until commit 95d3c10)

Here are some key observations to aid the review process:

🧪 No relevant tests
🔒 No security concerns identified
✅ No TODO sections
🔀 No multiple PR themes
⚡ No major issues detected

@github-actions

Copy link
Copy Markdown
Contributor

Persistent review updated to latest commit 647b599

@github-actions

github-actions Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

PR Code Suggestions ✨

Latest suggestions up to 95d3c10
Explore these optional code suggestions:

CategorySuggestion                                                                                                                                    Impact
General
Fix likely incorrect CVE year in note

The CVE identifier CVE-2026-35554 appears to reference a future year (2026), which
is likely a typo. Verify the correct CVE number (e.g., CVE-2025-XXXXX) and update
the release note to avoid publishing incorrect security references.

release-notes/opensearch-security.release-notes-2.19.6.0.md [7]

-* Update Kafka to 3.9.2 to resolve CVE-2026-35554 and other security issues ([#6089](https://github.com/opensearch-project/security/pull/6089))
+* Update Kafka to 3.9.2 to resolve CVE-2025-35554 and other security issues ([#6089](https://github.com/opensearch-project/security/pull/6089))
Suggestion importance[1-10]: 7

__

Why: The CVE identifier CVE-2026-35554 references year 2026, which is suspicious and likely a typo. However, the suggested replacement CVE-2025-35554 is a guess, so the user should verify the actual correct CVE number.

Medium

Previous suggestions

Suggestions up to commit 647b599
CategorySuggestion                                                                                                                                    Impact
General
Verify CVE identifier year is correct

The CVE identifier CVE-2026-35554 appears to use a future year (2026) which is
unusual and likely a typo. Verify the correct CVE identifier (e.g., CVE-2025-...)
before publishing the release notes, as incorrect CVE references can mislead users
about the security context.

release-notes/opensearch-security.release-notes-2.19.6.0.md [7]

-* Update Kafka to 3.9.2 to resolve CVE-2026-35554 and other security issues ([#6089](https://github.com/opensearch-project/security/pull/6089))
+* Update Kafka to 3.9.2 to resolve CVE-2025-35554 and other security issues ([#6089](https://github.com/opensearch-project/security/pull/6089))
Suggestion importance[1-10]: 8

__

Why: The CVE identifier CVE-2026-35554 uses a future year (2026), which is highly likely a typo for CVE-2025-35554. Incorrect CVE references in release notes can mislead users about security implications, so this is an important catch.

Medium

Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
@github-actions

Copy link
Copy Markdown
Contributor

Persistent review updated to latest commit 95d3c10

@peterzhuamazon peterzhuamazon merged commit 9a63f46 into opensearch-project:2.19 Jun 26, 2026
134 of 144 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants