Maven latest might be misused for respectLatest
#36927
Unanswered
Shegox
asked this question in
Request Help
Replies: 3 comments 11 replies
-
|
Thanks for your investigation. So it sounds like the |
Beta Was this translation helpful? Give feedback.
11 replies
-
|
That would be great :) |
Beta Was this translation helpful? Give feedback.
-
|
Revert of the revert is here, with additions: #37541 @Shegox WDYT? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, sorry for the very late response here. This is the config I've been testing with: I have also tried adding respectLatest: true to every packageRules block, but it does not change anything. |
Beta Was this translation helpful? Give feedback.
-
|
Please share the full logs |
Beta Was this translation helpful? Give feedback.
-
|
Here are the full logs for 1 repository. There's ~80 log lines with "Setting respectLatest=false for maven ...", also for the packages where we explicitly want respectLatest to be true. |
Beta Was this translation helpful? Give feedback.
-
|
I'd like to chime in with a rather specific case: I just had the following case where <versioning>
<latest>5.2.0</latest>
<release>5.2.1</release>
<versions>
<!-- ... -->
<version>5.2.0</version>
<version>5.2.1</version>
</versions>
<lastUpdated>20251104103941</lastUpdated>
</versioning>(5.2.1 was deployed only a little more than an hour after 5.2.0) Any thoughts on that? Thanks! PS: We are using the floating tag |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
We just stumbled over this discussion. Given the artifact We are using self-hosted Renovate 42.80.2, but we only get the desired behavior with Renovate prior to 40.0.0 (original PR #35515) or between 41.37.8 (revert #37021) and 41.78.1 (re-revert #37541), after 41.79.0 SP1 isn't selected by Renovate. Somehow Renovate still looks at |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
v41.25.0 / GitHub Enterprise Server
Please tell us more about your question or problem
With a recent change Renovate started to respect the
latestvalue from the maven-metadata.xml (see #35515) under the assumption thatlatestin maven, similar tonpmwhere it contains the highest stable version.After some internal problems and other public discussions (#36893, #36309) I think we might be misusing/understanding the
latest-version and it actually not lists the highest stable version, but rather the newest version. In semantic versioning these might be patch releases of a previous minor version and not the actually intended versionTo determine this I looked through some public documentation
According to the official spec
latestis defined as:Some other documentation highlighted as well that this includes the "newest published version" and not nessecary the highest version:
This behavior matches as well the behavior we have seen internally in Artifactory where the latest version matches the newest version rather than the highest:
The intended latest version would be
3.5.0, but because3.4.4was uploaded last and thus set by maven/the repository aslatest.I wasn't yet able to fully determine if this is just a limitation of Artifactory, but would be curious if anyone have seen the opposite scenario (e.g. someone actively setting
latestto indicate a "stable" version (or not setting it during a upload to indicate a unstable version))?Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions