Can Renovate create new PR's instead of updating existing ones?

[Ali-Haider-24]

How are you running Renovate?

A Mend.io-hosted app

Which platform you running Renovate on?

GitHub.com

Which version of Renovate are you using?

43.259.2

Please tell us more about your question or problem

Is it possible to configure Renovate in a way where it will create new PR's for a dependency that has multiple releases, instead of updating an existing PR?

For example, suppose there is a a new version of a module (e.g. 1.1.0) is released. Renovate creates a branch and PR for the dependency update. Before we merge that PR, version 1.1.1 of the module is released. Can we configure Renovate to create a brand new PR for version 1.1.1 instead of updating the existing PR?

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[RahulGautamSingh]

https://docs.renovatebot.com/presets-default/#separatemultipleminorreleases

[Ali-Haider-24]

Thanks for that... so there is no option to separate each patch version of dependencies into individual branches/PRs?

[RahulGautamSingh]

https://docs.renovatebot.com/presets-default/#separatepatchreleases

It was just below the above :)

[Ali-Haider-24]

Sorry, I might be misunderstanding that config option. Is it saying that each distinct patch release of a module will have a different PR?

[Ali-Haider-24]

According to this documentation https://docs.renovatebot.com/configuration-options/#separateminorpatch - this configuration option will create separate PR's for patch and minor releases. But it will not create a new PR for every new patch release if I understand correctly.

[RahulGautamSingh]

Sorry, my bad.

https://docs.renovatebot.com/presets-default/#separatepatchreleases won't separate multiple patch releases, that is not supported yet.

I checked the code and the logic for the separate patch releases function exists but is commented out.

renovate/lib/workers/repository/process/lookup/bucket.ts

Lines 65 to 74 in 26c1641

	// If we reach here then we know it's a patch release
	/* future option
	if (separateMultiplePatch) {
	const toPatch = versioningApi.getPatch(newVersion);
	if (toPatch !== null && separateMultiplePatch) {
	return `v${toMajor}.${toMinor}.${toPatch}`;
	}
	}
	*/

PR welcome for this.