Skip to content

Do a version comparison to make sure the "affected" field matches the package for go call analysis #1559

@another-rex

Description

@another-rex

Do a version comparison to make sure the "affected" field matches the package for go call analysis.

There could be a really unlikely scenario where different functions are affected in different version ranges of a record, and only one of those ranges have symbol information filled in.

(There are currently no records like this, and while it's semantically possible, I don't believe Go will ever publish such a record).

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