Skip to content

Review use of VersionNumber/VersionSpec/`Strings in compat checking #79

@mmiller-max

Description

@mmiller-max

Not sure how urgent this is, but we are not doing things quite right, e.g. when getting the compat field from a Project.toml it's set as a VersionNumber, where as actually it represents a VersionSpec (effectively a range).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions