Skip to content

Rationale for ~0.0.0 being equal to >=0.0.0? #254

Open
@michaellee1019

Description

I noticed that this library treats the ~0.0.0 constraint as equal to >=0.0.0 (all versions are valid against the constraint) and was implemented in 429e95e. Before seeing this I was thinking that 0.1.0 and greater would fail the constraint against ~0.0.0. I couldn't find any rationale for this decision and wondering if any additional context could be provided.

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