Enforce fixVersion validation when searching for rebuild dependencies - #769
Merged
lbarcziova merged 1 commit intoAug 20, 2026
Conversation
The triage and sibling rebuild agents search for dependency CVE trackers by CVE ID and component, but never validated that the found tracker targets the same RHEL version stream. With multiple z-streams now active (10.0.z, 10.1.z, 10.2.z, 10.3), the LLM could pick a tracker from a different stream, causing the buildroot check to use the wrong NVR and produce nonsensical postpone messages (e.g. "waiting for golang (golang-1.26.5-1.el10_0)" on a rhel-10.3 ticket). Changes: - Instruct triage agent to validate that dependency issues have a matching fixVersion (same major.minor) and never use trackers from different streams - Add rebase/update ticket fallback when no CVE tracker exists for the target stream (with requirement to verify the rebase fixes the CVE) - Fall back to clarification-needed instead of using a wrong-stream tracker - Apply same fixVersion validation to sibling rebuild analysis Assisted-by: Claude Opus 4.6
lbarcziova
marked this pull request as ready for review
August 20, 2026 11:21
TomasKorbar
self-requested a review
August 20, 2026 12:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The triage and sibling rebuild agents search for dependency CVE trackers by CVE ID and component, but never validated that the found tracker targets the same RHEL version stream. With multiple z-streams now active (10.0.z, 10.1.z, 10.2.z, 10.3), the LLM could pick a tracker from a different stream, causing the buildroot check to use the wrong NVR and produce nonsensical postpone messages (e.g. "waiting for golang (golang-1.26.5-1.el10_0)" on a rhel-10.3 ticket).
Changes:
Assisted-by: Claude Opus 4.6