feat(datasource/maven): set latest tag ignored by default #37541
Conversation
This file contains hidden or 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
This reverts commit 9f63f4a.
|
FYI @Shegox |
|
I think as a optionally opt-in this is a great solution 👍 (I still think that the official spec/implementation of the maven registry didn't intend for this use case) |
|
Yes, not I think about it - using the term "latest" to implicitly mean "stable" is not a good idea in any ecosystem. We've spent much time in this project alone dealing with the nuances between latest, last, stable, more recent, etc. |
viceice
approved these changes
Aug 18, 2025
|
🎉 This PR is included in version 41.79.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
Reintroduces latest/release tags for Maven datasource, but this time sets respectLatest to false if a latest tag is found. When this feature was released originally, there were too many situations where registry latest tags were unreliable (e.g. the most recent version pushed, not some "stable" latest). With this new approach, users have to explicitly opt in.