Renovate doesn't suggest update for maven package. #43083
Replies: 2 comments 2 replies
-
|
Renovate's Maven versioning should support this: Could you share the relevant Renovate config/packageRules and debug logs for this dependency lookup? I think it may be something not related to the versioning machinery. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions. No logs at allIf you haven't posted any log yet, we need you to find and copy/paste the log into the issue template. Finding logs on hosted appSelect me to read instructionsIf you use the Mend Renovate app (GitHub):
Finding logs when self-hostingSelect me to read instructionsRead the Renovate docs, troubleshooting, self-hosted to learn how to find the logs. Formatting your logsSelect me to read instructionsPlease put your logs in a If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate CLI
Which platform you running Renovate on?
GitLab (.com or self-hosted)
Which version of Renovate are you using?
43.160.6
Please tell us more about your question or problem
I have a library that I publish as maven artefact and want to consume it in another maven project as dependency.
The versioning is as follows:
1.x, 1.x.1, 1.x.2....
Usually, we start with 1.x and then want to upgrade to 1.x.1 and so on as soon as it's available.
It seems that Renovate suggests and performs the update to e.g. 1.x.2 once we set 1.x.1 manually.
But Renovate doesn't suggest 1.x to 1.x.1.
What are our options here?
Does publishing 1.x.0 resolve this issue?
Logs (if relevant)
No response
Beta Was this translation helpful? Give feedback.
All reactions