fix(manager/gradle-wrapper): refresh Gradle lockfile after wrapper update #23081
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.
Changes
Adds an additional step to
gradle-wrapper
manager to update optionally existing gradle lockfiles. This is needed in case lockfiles and gradle built-in plugins with hard-coded versions likejacoco
orpmd
are used.If no lock files exist,
updateArtifacts
of thegradle
manager returns gracefully.Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via:
Test repo: renovate-demo/23071-renovate-gradle-lockfile-test#1