Reported last version of dependencies is outdated

[PLNech]

First of all, congratulations for this very helpful plugin! 😄

When running dependencyUpdates, the reported last version of com:algolia:algoliasearch-android is 2.5.0. However, the last available in mavenCentral is 3.5.0, which is also the last tag on GitHub.

What could explain the wrong version being reported? Maybe this is similar to #103?

[ben-manes]

The latest version on jcenter is 2.5.0. If you include mavenCentral it should query and find 3.5.0, but does not query repositories you have not included. You probably need to unlink jcenter to have it mirror central.

[PLNech]

Oh, this explains that!
Thank you, I'll close the issue and check on my side what stopped working in our release process.

[ben-manes]

Easiest solution is to delete your repositories on JCenter. When you take ownership of a dependency from Central, that "linking" stops the automatic mirroring and JCenter assumes you will not publish through them. If you do, then you have configure the account to sync with Central by providing your credentials. But if you still publish to Central instead, but took ownership to see the stats, then you'll stop seeing updates to your repositories reflected in JCenter.

I had the same problem with Caffeine, with JCenter reps reaching out because they received complaints and asked if they could unlink. It is a very confusing UX.

My recommendation is to either delete your JCenter repositories or switch the release process to use JCenter with Central sync. The JCenter stats wasn't worth the hassle to change my workflow, so I deleted the remaining ones I had.