Bump Versions

Bump Versions

Update project dependency versions to their latest stable releases using the right tool for each build system.

Detect the Build System

Before updating anything, identify which build system the project uses:

• gradle/libs.versions.toml → Gradle version catalog (docs)
• libs.versions.toml at the project root alongside module.yaml → Kotlin Toolchain version catalog (docs)
• pom.xml → Maven project (docs)

If multiple build systems coexist, update each one independently.

Gradle Version Catalog

Use caupain to discover available updates, then apply them to the catalog. On macOS, install via brew install deezer/repo/caupain.

1. Run caupain in the project root.
2. Update only version values in the [versions] section of gradle/libs.versions.toml.
3. Preserve exact formatting — quotes, spacing, alignment, line order.
4. Never modify .gradle.kts or .gradle build files.
5. Never run Gradle builds for validation.

# Before
kotlin = "2.3.0"

# After
kotlin = "2.4.0"

Kotlin Toolchain Version Catalog

Use caupain with the root-level catalog, then update both the catalog and Kotlin Toolchain module/project files. Refer to the Kotlin Toolchain documentation for current Toolchain guidance instead of guessing.

1. Run caupain -i libs.versions.toml in the project root.
2. Update version values in libs.versions.toml (at the project root, not under gradle/).
3. After updating the catalog, scan all module.yaml, template yaml files (referenced via apply: in module.yaml), and project.yaml for inline version values that match a bumped version, and update them to match.
4. Preserve exact formatting — quotes, spacing, alignment, line order.
5. Never modify Kotlin Toolchain build config beyond version bumps.
6. Do not run builds, tests, or any ./kotlin command; this skill only makes version changes.

# libs.versions.toml — Before
kotlin = "2.3.0"

# libs.versions.toml — After
kotlin = "2.4.0"

# module.yaml — Before
settings:
  kotlin:
    version: 2.3.0

# module.yaml — After
settings:
  kotlin:
    version: 2.4.0

Maven POM

Use the Maven Versions Plugin to discover available updates, then apply them to pom.xml.

1. Run ./mvnw clean versions:display-dependency-updates versions:display-plugin-updates versions:display-property-updates in the project root.
2. Update only <properties> values in pom.xml with the reported latest versions.
3. Preserve exact formatting — indentation, tag style, line order.
4. Never run any other Maven commands for validation.

<!-- Before -->
<kotlin.version>2.3.20</kotlin.version>

        <!-- After -->
<kotlin.version>2.3.21</kotlin.version>

Rules

• Always use the appropriate tool (caupain or mvnw versions:) to discover latest versions — never manually check Maven Central or GitHub. These tools handle transitive compatibility and release metadata far more reliably than manual lookups.
• Only change version values. Never alter keys, property names, dependency coordinates, or structural formatting.
• Prefer stable releases over pre-release/beta unless the project already uses a pre-release version for that dependency.
• Never run builds, tests, or ./kotlin commands for version-only updates.
• Make no other changes to the codebase beyond version bumps.