Renovate create the pull request too early when there are a lot of packages sharing the same version

[JavierSegoviaCordoba]

How are you running Renovate?

WhiteSource Renovate hosted app on github.com

Please select which platform you are using if self-hosting.

No response

If you're self-hosting Renovate, tell us what version of Renovate you run.

No response

Describe the bug

In Gradle Plugins repo, I have like 10-20 projects sharing the same version, but Renovate is not waiting until all projects are available in the remote repositories to create the PR.

As this PR is created too early, it fails because some of the packages are available with the new version, but others are only available with the older version until the next 5-15 minutes. So I have to rerun the GitHub workflow manually or select the PR to be rebased.

Relevant debug logs

Logs

Copy/paste any log here, between the starting and ending backticks

Have you created a minimal reproduction repository?

No reproduction, but I have linked to a public repo where it occurs

[rarkins]

Try setting stabilityDays=1

[JavierSegoviaCordoba]

Is it possible to change this one to be in hours or minutes?

If not, should I create a feature request for this one?

stabilityHours=1 or stabilityMinutes=30

[rarkins]

It would need code changes, but I am happy for us to do it. Ideal for me would be:

• Rename it to be a bit more generic (e.g. "releaseDelay", but better)
• We retire/migrate stabilityDays
• Define a simple format for duration - or find one which already exists - so that it can be e.g. 1d2h3m. We might find use for such a format elsewhere

[JavierSegoviaCordoba]

I like your idea and it is better to have only one property

[HonkingGoose]

We have another open issue ¹ that's about "waiting until all dependencies in a group have new versions before opening/merging PR". It sounds similar in concept:

The use case here is that you still want fast updates, but you don't want to open a PR for a group until some required deps have new versions, ensuring they are always updated together.

I also found a issue that wants to "force same versions inside package group", which also sounds related. ²

I don't know which issues we want to keep/close.

I'll let @rarkins decide what to do with each issue. 😉

Footnotes

1. https://github.com/renovatebot/renovate/issues/9739 ↩

2. https://github.com/renovatebot/renovate/issues/12310 ↩

[rarkins]

Duplicate of #12310