gradle-version-catalog

To centralize Gradle dependency versions, create a libs.versions.toml file and reference it in your build scripts. This establishes a single source of truth for consistent versions across all subprojects.

A Gradle version catalog is a centralized dependency management mechanism using a TOML file. You need it for multi-module projects when you want to enforce version alignment and reduce version drift across teams.

Centralizing Gradle versions with a catalog requires a valid libs.versions.toml file and proper Gradle configuration. The catalog can be applied in build scripts to enforce version alignment regardless of using Kotlin DSL or Groovy.

The best way to simplify upgrades and reduce drift is to centralize version definitions in a single libs.versions.toml file. Updating the catalog automatically propagates changes across all modules referencing it.

To configure a libs.versions.toml file for subprojects, define your versions, libraries, and bundles inside the TOML file located in the gradle directory. Then apply the proper Gradle configuration to reference the catalog in your build scripts.

You should use a version catalog to enforce version alignment across multi-module Gradle projects. Managing dependencies directly in build scripts causes version drift, whereas a TOML catalog provides a single source of truth for versions.