Skip to content

Versions on published on npm have no corresponding release here #520

@crass

Description

@crass

A glaring example is version 17.7.2 from 3 years ago, which has over 50 million downloads, yet no tag or release here. There's not even a 17.x.x branch. Did some branches get deleted in a cleanup? I saw #320 which noted that 13.1.2 was not tagged at that time because it was not common to go back that many releases. This was from late 2020, a couple years before 17.7.2, which indicates that either after this issue tags of new releases weren't always created or tags were deleted. That issue notes that releases were done from the 13.x.x branch, but as noted above, no branch exists for 17.x.x. It does seem odd that the most popular version on npm does not have a corresponding branch here.

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