Skip to content

cmd/go: add a 'go mod why' mode to answer “why this specific version?” #28800

@bcmills

Description

@bcmills

As noted in #28795 (comment), today we can use go mod graph to figure out which module imposes a particular version of a dependency, then use go mod why to figure out why that module is included.

However, that's two queries to answer what is logically a single question: “why was this version of the module selected?” Perhaps we should add a go mod why flag to answer that question more directly.

(CC @rsc @myitcv @thepudds)

Metadata

Metadata

Assignees

No one assigned

    Labels

    FrozenDueToAgeGoCommandcmd/goNeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.modules

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions