This message was deleted.

No and half of. If you use dynamic versions (like

+

or

1.+

or ranges), then the latest is used, but this should imho - if at all - used with dependency locking and making sure only concrete versions are published. If you define concrete versions (which I prefer), then there are two major plugins that can help you. The

gradle-versions

plugin of ben manes which displays all outdated versions and what their latest is and with some restrictions the

refreshVersions

plugin of jmfayard that only works properly when you use proper Maven repositories and that I only like to use when I also use version catalogs as then it can do its magic in there, otherwise it requires another non-standard centralized versions file and using

_

as version when declaring the dependencies. The latter is faster as it only works within its restrictions and can optimize and will insert as comments all newer versions for you to pick, the former needs longer and only displays the latest version, but works with any repository and dependency declaration layout.