Skip to content

installed versions is a true reflection of currency, not requirements constraints? #38

@brabster

Description

@brabster

Hi there, nice idea!

My requirements file may be allow updating to the latest version of dependencies (and so may show as up to date with libyear) but if I cache my dependencies and last updated them two years ago then the actual libraries making up my application could be hundreds of "libyears" behind current.

Is that by design, if so what is the rationale?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions