Skip to content

Add "max major increment" option with sensible default #20772

@rarkins

Description

@rarkins

What would you like Renovate to be able to do?

Avoid upgrading from normal-looking versions to high versions like daily releases

If you have any ideas on how this should be implemented, please tell us here.

Example: repository currently uses 19.2. There exists a new version 20.0, but also 2023.03.03 or something like that.

Today, Renovate will take the 2023 one. Instead, we should have a new configuration option like maxMajorIncrement defaulting to perhaps 50. which filters out any releases which are >50 major releases higher than the current.

I think this would produce less problems by default than having no limit does today.

Is this a feature you are interested in implementing yourself?

No

Metadata

Metadata

Assignees

No one assigned

    Labels

    mend:customer-requestIssues requested on behalf of a Mend customerpriority-3-mediumDefault priority, "should be done" but isn't prioritised ahead of others

    Priority

    None yet

    Datasource

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions