Display your sbt project's dependency updates.

Update information is obtained from the maven metadata. There is also a limited support for Ivy repositories hosted on BinTray.

If your project uses crossScalaVersions you will be presented only with updates available for all scala versions.

sbt 0.13.9 and later. sbt 1.x is supported since version 0.3.1.

Create a ~/.sbt/1.0/plugins/sbt-updates.sbt file (for sbt 1.x series), or ~/.sbt/0.13/plugins/sbt-updates.sbt (for sbt 0.13.x series) with the following content:

addSbtPlugin("com.timushev.sbt" % "sbt-updates" % "x.x.x")

The latest version is

Choose one of versions available on BinTray or the latest one. Then create a ~/.sbt/1.0/plugins/sbt-updates.sbt file (for sbt 1.x series), or ~/.sbt/0.13/plugins/sbt-updates.sbt (for sbt 0.13.x series) with the following content:

resolvers += Resolver.bintrayIvyRepo("rtimush", "sbt-plugin-snapshots")
addSbtPlugin("com.timushev.sbt" % "sbt-updates" % "x.x.x-y+gzzzzzzz")

Note, that snapshots are not updated automatically.

• dependencyUpdates: show a list of project dependencies that can be updated,
• dependencyUpdatesReport: writes a list of project dependencies to a file.

• dependencyUpdatesReportFile: report file location, target/dependency-updates.txt by default.
• dependencyUpdatesFilter: filter matching dependencies that should be included to update reporting.
• dependencyUpdatesFailBuild: dependencyUpdates task will fail a build if updates found.
• dependencyAllowPreRelease: when enabled, pre-release dependencies will be reported as well.

• dependencyUpdatesExclusions: filter matching dependencies that should be excluded from update reporting.

You can exclude some modules from update checking:

dependencyUpdatesFilter -= moduleFilter(organization = "org.scala-lang")

If sbt-updates is installed in your global file you can get updates for sbt plugins by using the reload plugins command:

> reload plugins
...
> dependencyUpdates
[info] Found 2 dependency updates for project
[info]   com.timushev.sbt:sbt-updates          : 0.3.0  -> 0.3.4 -> 0.4.3
[info]   org.scala-lang:scala-library:provided : 2.10.6          -> 2.12.4
> reload return

Only plugins defined in a project are checked, there is currently no way to check updates for global plugins.

You can also check updates for dependencies and sbt plugins with:

sbt ";dependencyUpdates; reload plugins; dependencyUpdates"

It is preferred to use sbt-updates as a global plugin. Nevertheless, there might be cases when you want to use sbt-updates as a project plugin. In that case, add the plugin definition to project/sbt-updates.sbt. You can then use dependencyUpdates target to find updates for your project. But this way you won't be able to check sbt plugin updates. In order to check both dependency updates and sbt plugin updates, add the plugin to both project and meta project i.e project/sbt-updates.sbt and project/project/sbt-updates.sbt and run:

sbt ";dependencyUpdates; reload plugins; dependencyUpdates; reload return"

sbt-updates relies on the repository Maven metadata. If you want to get update notifications for artifacts published by other sbt projects, you should ensure that metadata is updated correctly. One possible way to achieve this is to use sbt-aether-deploy.

In order from left, the result shows current version, patch update version, minor update version and major update version.

> dependencyUpdates
[info] Found 3 dependency updates for test-project
[info]   ch.qos.logback:logback-classic : 0.8   -> 0.8.1 -> 0.9.30 -> 1.0.13
[info]   org.scala-lang:scala-library   : 2.9.1 -> 2.9.3 -> 2.10.3
[info]   org.slf4j:slf4j-api            : 1.6.4 -> 1.6.6 -> 1.7.5