Exclude parent pom 5.x from renovate updates #763
Merged
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.
Exclude parent pom 5.x from renovate updates
Projects configured from the archetype most often prefer to depend on the last release of a recent LTS line. The archetype currently requires Jenkins 2.440.3 or newer. When we switch to parent pom 5.x, we'll need to require Jenkins 2.475 (weekly) or Jenkins 2.479.x (LTS).
I think it will be several months before we're ready to switch the archetype to use plugin parent pom 5.x. Until that time, this configures renovate to only recommend versions less than 5.x
Testing done
Installed and ran the renovate-config-validator locally with commands:
$ nvm install --lts
$ npx --yes --package renovate -- renovate-config-validator
Before this change, reported that migration was needed. After this change, it no longer reports that migration is needed.
Does not check that the package name is correct, though I checked that with
git grep
.Submitter checklist