Skip to content

Don't handle caret as update #1

@ehs5

Description

@ehs5

For example, if old file is 3.5.0 and new file is ^3.5.0, this is treated as an update.

We should probably keep the caret when displaying, but make sure we don't include the caret in string when checking if package has been updated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions