Skip to content

Does not handle interwoven releases #31

@timdorr

Description

@timdorr

Right now in RR, there is this tag listing:

react-router@7.1.0
react-router@6.28.1
react-router@7.1.0-pre.0
react-router@6.28.1-pre.0
react-router@7.0.2
react-router@7.0.2-pre.0
react-router@7.0.1
react-router@7.0.0
...

At the moment, the action is comparing the 7.1.0 release with the 6.28.1 release. This is creating a ton of issue comments on the RR repo (such that the action is failing due to rate limits!). It will be resolved on the next 7.x release, but this will continue to be an issue if we have to create 6.x releases in the future.

I believe the fix would be to check a set of recent versions (10?) for the most recent sequential semver release in that set and make it the previous value.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions