chore: explicitly specify maven central location for renovate-bot version lookups #3374
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.
From #3372, the files
.cloudbuild/
directories aren't getting updated to use the latest java-shared-config version. From the renovate logs, there appears to be a difference in the registry urls used when looking up versions from maven central.Registry used when an update to the latest version is successfully made to
1.12.0
:For
.cloudbuild/
files, the registryUrl defaults tohttps://repo.maven.apache.org/maven2
:Explicitly specifying registryUrl to
https://repo1.maven.org/maven2
worked in https://github.com/mpeddada1/forking-renovate-repro