Can messages be generated for dependencies that are years and years out of date? #9293
Unanswered
aSemy
asked this question in
Request Help
Replies: 2 comments 3 replies
-
You would probably be interested to follow #5535 for when it's implemented |
Beta Was this translation helpful? Give feedback.
2 replies
-
I suspect we have some issues open for this feature where Renovate helps with deprecated/dead dependencies. The issues listed below might be duplicates, or they might not be. At the very least they seem to cover similar ground.
I'll let @rarkins decide on what to keep and mark as duplicate of... 😉 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'd like to modernise a large, old project that has a lot of dependencies. I think a dependency bot like Renovate could help - but I have one specific question (see title).
For example, there is a dependency declared on com.jayway.awaitility:awaitility:1.7.0. This dependency was released in 2015.
From what I understand, Renovate would not see any problem with this dependency, as it is on the latest version. However, really it's out of date. The dependency was moved to org.awaitility:awaitility, which released version 4 last year.
Other dependencies are in a similar situation (and not just in Maven). They have been abandoned, or replaced.
Ignoring the task of how to update these old dependencies, can Renovate provide these warnings, so I can make a start?
Beta Was this translation helpful? Give feedback.
All reactions