Closed satorg closed 2 years ago
sbt-updates
relies on the metadata files for maven repositories, and the maven-metadata.xml
for fs2-core doesn't actually contain 3.2.7
. This seem to be the same issue as in MVNCENTRAL-6820 — the newer versions are most likely published to the "new" s01 Sonatype server, but it looks like there was a build of an older version that published artifacts to the "old" Sonatype server, and this screwed up the metadata. Hopefully, it will get fixed next time fs2 publishes any artifact.
That said, the same can potentially affect any library backporting fixes to older versions, so maybe I should make sbt-update
check not only the metadata file, but also the directory listing for Maven Central as well.
Actually, I did more checks on that and noticed that the last FS2 version that sbt-updates still able to find updates for is "3.0.0" – it shows that "3.0.1" is available. But seems that all other subsequent versions are not detected by sbt-update anymore.
Fixed in #317
Cool, thanks!
Versions used:
Consider this simple
build.sbt
:then run
sbt dependencyUpdates
:So no updates found although there's definitely a newer version: v3.2.7
The plugin still works for all other libraries I got a chance to try.