alejandrohdezma / sbt-dependencies   0.1.0

Manage SBT dependencies from a single YAML file with version markers, auto-updates, and cross-project support

Add the following line to your project/project/plugins.sbt file:

addSbtPlugin("com.alejandrohdezma" % "sbt-dependencies" % "0.2.0")

Adding the plugin to project/project/plugins.sbt (meta-build) allows it to manage both your build dependencies and your project dependencies.

Create a project/dependencies.yaml file listing your dependencies:

sbt-build:
  - ch.epfl.scala:sbt-scalafix:0.14.5:sbt-plugin
  - org.scalameta:sbt-scalafmt:2.5.4:sbt-plugin
  - io.get-coursier::coursier:2.1.24

my-project:
  - org.typelevel::cats-core:2.10.0
  - org.scalameta::munit:1.2.1:test

Groups correspond to:

• sbt-build: Dependencies for your build definition (plugins and libraries used in build.sbt)
• <project-name>: Dependencies for a specific project (matches the SBT project name)

The plugin automatically populates libraryDependencies for each project based on its group.

Dependencies follow this format:

org::name:version:config   # Cross-compiled (Scala) dependency with configuration
org::name:version          # Cross-compiled (Scala) dependency
org::name                  # Cross-compiled, latest version resolved automatically
org:name:version:config    # Java dependency with configuration
org:name:version           # Java dependency
org:name                   # Java, latest version resolved automatically

Supported configurations: compile (default), test, provided, sbt-plugin, etc.

Dependencies with Scala version suffixes in their artifact name are automatically filtered based on the current scalaVersion:

my-project:
  - org.example:my-lib_2.13:1.0.0  # Only added when scalaVersion is 2.13.x
  - org.example:my-lib_2.12:1.0.0  # Only added when scalaVersion is 2.12.x
  - org.example:my-lib_3:1.0.0     # Only added when scalaVersion is 3.x
  - org.example:other-lib:1.0.0    # Always added (no suffix)

This is useful for dependencies that are published with Scala-specific variants but aren't cross-compiled in the usual way (e.g., some native libraries or Java libraries with Scala-specific modules).

Control how dependencies are updated using version markers:

Displays the library dependencies for the current project in a formatted, colored output. Shows both direct dependencies and those inherited from dependent projects (via .dependsOn).

sbt> showLibraryDependencies

• Green = direct dependencies
• Yellow = inherited from other projects

Updates dependencies in the current project to their latest versions.

sbt> updateDependencies # Update all project dependencies
sbt> updateDependencies org.typelevel: # Update all `org.typelevel` dependencies
sbt> updateDependencies :cats-core # Update `cats-core` from any organization
sbt> updateDependencies org.typelevel:cats-core # Update specific dependency

Installs a new dependency to the current project.

sbt> install org.typelevel::cats-core:2.10.0
sbt> install org.typelevel::cats-effect # Resolves latest version
sbt> install org.scalameta::munit:1.2.1:test

Updates dependencies in the meta-build (project/dependencies.yaml, group sbt-build).

sbt> updateBuildDependencies

Installs a new dependency to the meta-build.

sbt> installBuildDependencies ch.epfl.scala:sbt-scalafix:0.14.5:sbt-plugin

Updates everything: the plugin itself, build dependencies, and project dependencies.

sbt> updateAllDependencies

Updates the sbt-dependencies plugin itself in project/project/plugins.sbt.

sbt> updateSbtDependenciesPlugin

alejandrohdezma