Prepare for having Renovate add separate PRs for branch_9x #3057
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that main branch uses gradle version catalogs (#2706), dependency upgrades cannot be easily back ported to branch_9x anymore, unless the version catalogs are back ported as well.
Also, many features are removed in main that still exist in branch_9x, so we will miss out on certain dep updates if we only rely on manual backports.
Therefore I propose, and will test with dryRun, that @solrbot files separate PRs for branch_9x, using the baseBranches feature. For that to work we define
useBaseBranchConfig=merge
so that we can userenovate.json
on this branch as an overlay, specifying configs that differ from main and giving a PR title suffix etc. Steps:renovate.json
config in branch_9x, which targets oldversions.properties
and acts as overlaybaseBranches
anduseBaseBranchConfig
Once Solr 10 is released, we can redefine this to target latest
branch_9_x
which will have a long life in bugfix mode.