Skip to content

Ignore unstable version in outdated dependency logic #1456

@idleberg

Description

@idleberg

Description

In the list of dependencies, a gap in major versions is indicated with red colour and a warning symbol. This is a useful feature, but IMHO it should not check against unstable versions.

Example

Image

c12 latest stable version: v3.3.3
c12 latest version: 4.0.0-beta.2

However

What's problematic is that version 4.0.0-beta.2 uses the default dist-tag latest, so one might argue that the problem is on the developer side.

Image

Still, I wanted to bring it up and propose a fix. You can decide how to deal with it.

Metadata

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