Renovate not updating relocated dependencies #8104
Replies: 1 comment 26 replies
-
Can you clarify what/where exactly this is? |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, the 404 outlined refers to an artifact that is 4 years old, wondering that such an oldie is still relevant. Anyway, should I add the arg to my renovate.json or do you want to test it on your fork? |
Beta Was this translation helpful? Give feedback.
-
|
Recently, we've introduced mandatory POM file presence check (by making HEAD request), in order to filter versions which are present in It works great for Maven central, but for some other repos there are false hits. In your case, that's because we look available versions here: BTW we already have the issue for that. But for quick workaround, |
Beta Was this translation helpful? Give feedback.
-
|
Oic, interesting. But that is only relevant to nested poms, isn't it? For the previous issue, would I need to use gradle-lite and add all repositories as |
Beta Was this translation helpful? Give feedback.
-
|
We already merged the fix, so now (soon) gradle-lite should detect |
Beta Was this translation helpful? Give feedback.
-
|
@zharinov maybe we are better off not to do the HEAD by default and either:
|
Beta Was this translation helpful? Give feedback.
-
Heyo,
I was wondering if renovate requires an additional config entry to update relocated/shaded dependencies.
Renovate raised this pull request and updated the version from 1.7 to 1.8. However, the version of the shadow jar task has either been ignored or not recognized, as it is still 1.7 in the pr named.
Is there anything I forgot?
Cheers
Beta Was this translation helpful? Give feedback.
All reactions