Force same versions inside package group

[languitar]

What would you like Renovate to be able to do?

With typing support being more accepted in the Python ecosystem, we often see packages like click and types-click, where the latter contains the typing annotations for the former. Both packages use the same versions to keep referential integrity between actual production code and the type annotations. There, none of them should be updated in isolation and to a differing package version.

I'd like to have a feature that indicates per package group that all contained packages must always be updated to the same version and no MR will be created without this precondition being fulfilled.

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

I've found this feature request: #9739. Maybe this one is a specialization of that request. But I think explicitly forcing the same version update has not been requested in #9739.

Is this a feature you are interested in implementing yourself?

No

[rarkins]

What if they get out of sync though - suppress updates forever?

[languitar]

For some of these combinations the pypi packages originate from the same repository. So it's pretty safe to assume this fixed versioning in that case.

But yes, if I really want that constraint, then no MR should be created if it cannot be fulfilled. As it's not the default that shouldn't be a problem for others.

[rarkins]

What about adding stabililityDays to be a value high enough that you are pretty sure they will all have been published by the time it expires? It's not a perfect solution but I'd guess it's a decent workaround.

[languitar]

Yes, that's a workaround we could use, but some uncertainty remains there.

[JavierSegoviaCordoba]

@rarkins any news about releaseDelay you suggested here: #12133 (comment)

[rarkins]

I'm not sure there's any feature request open for it yet, so you could start with that

[JavierSegoviaCordoba]

Done: #16875

[github-actions]

Hi there,

Get your issue fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this.

To get started, please read our guide on creating a minimal reproduction.

We may close the issue if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment.

Good luck,

The Renovate team