Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

MaxVersion flag does not properly handle version range validation in some cases #682

Copy link
Copy link

Description

@ZohaiAli
Issue body actions

When using the --maximum-version (-mv) flag, the tool throws a CommandValidationException if the provided version string is valid but lacks build or revision parts (e.g., 8.0).
This happens because Version.TryParse normalizes missing fields to -1, which causes unexpected comparison behavior later in the analysis phase.

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    Morty Proxy This is a proxified and sanitized view of the page, visit original site.