Skip to content

fix: correctly assign targetVersion for parent-update targets - #1121

Draft
RohithPariki wants to merge 4 commits into
OWASP:mainfrom
RohithPariki:fix-1007-cross-wired-version
Draft

fix: correctly assign targetVersion for parent-update targets#1121
RohithPariki wants to merge 4 commits into
OWASP:mainfrom
RohithPariki:fix-1007-cross-wired-version

Conversation

@RohithPariki

@RohithPariki RohithPariki commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

What changed and why

The targetVersion for parent-update was being incorrectly populated with the child dependency's safe version (targetChildVersion). During map insertion, if the parent was also flagged as a direct finding, its correct targetVersion could be overwritten by this incorrect child version due to version comparison sorting, resulting in cross-wired suggested commands.

This assigns currentVersion to targetVersion for parent-update targets, preventing incorrect version merging while correctly indicating no direct version change is needed in the UI.

Closes #1007

Fixes OWASP#1007. Assigns the parent's currentVersion instead of the child's targetChildVersion to the parent-update target, preventing incorrect version merging for direct dependencies.
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.

suggestedFixCommands emits a version that does not exist (cross-wired from another finding)

1 participant