Introduce option to assume that looked up maven data is specification compliant #32651
+17
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The current maven datasource lookup is not conform with the Maven standards and was only introduced because a few people used misconfigured maven repositories.
This PR introduces an experimental option
RENOVATE_X_MAVEN_LOOKUP_ASSUME_SPECIFICATION_COMPLIANT.If this is set, Renovate assumes that the looked up Maven Metadata conforms to specification and will skip some checks and requests.
Context
Fixes #27768
In the future it might be desirable to make this the default.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: