Drop-in replacement for sbt-release rebuilt on cats-effect IO, with hook-based customization, monorepo support, and Resource-safe lifecycle management.

Start with the plugin-specific onboarding guides:

• Single-project builds: docs/core/getting-started.md
• Monorepos: docs/monorepo/getting-started.md
• Full docs index: docs/README.md
• Release history and upgrade notes: CHANGELOG.md

Install in project/plugins.sbt:

addSbtPlugin("io.github.scalauser12" % "sbt-release-io" % "0.13.2")

The plugin auto-enables on all projects. Add a version.sbt:

ThisBuild / version := "0.1.0-SNAPSHOT"

First command:

sbt "releaseIO check with-defaults"

Read next:

• Core getting started
• Core customization walkthrough
• Core customization

Install in project/plugins.sbt:

addSbtPlugin("io.github.scalauser12" % "sbt-release-io-monorepo" % "0.13.2")

In build.sbt:

lazy val core = (project in file("core"))
lazy val api  = (project in file("api"))

lazy val root = (project in file("."))
  .aggregate(core, api)
  .enablePlugins(MonorepoReleasePlugin)

Each subproject needs its own version.sbt containing version := "0.1.0-SNAPSHOT". The monorepo plugin depends on the core plugin, so the shared releaseIO* keys are available transitively. Use releaseIOMonorepo to drive a release.

First command:

sbt "releaseIOMonorepo check with-defaults"

Read next:

• Monorepo getting started
• Selective release walkthrough
• Monorepo customization

Customization is layered. Pick the lowest level that solves your problem:

• CLI flags for one-off tweaks: with-defaults, skip-tests, cross
• Behavior toggles to flip defaults: releaseIOBehavior* / releaseIOMonorepoBehavior*
• Pre-answered prompts for non-interactive runs: releaseIODefaults*
• Task overrides to redefine a specific step: releaseIOPublishAction, releaseIOVcsTagName, the releaseIOVersioning* keys
• Hooks and policies to inject logic around phases: releaseIOHooks* / releaseIOPolicy* (and their releaseIOMonorepoHooks* / releaseIOMonorepoPolicy* counterparts)
• Resource hooks for anything acquired once per run (HTTP client, temp workspace, etc.): extend ReleasePluginIOLike[T] / MonorepoReleasePluginLike[T]

See docs/core/customization.md and docs/monorepo/customization.md for the full catalog.

For local rehearsal recipes, see docs/core/recipes.md and docs/monorepo/recipes.md. For rollback and recovery, see docs/core/operations.md and docs/monorepo/operations.md.

# sbt 1
sbt compile              # compile all modules
sbt test                 # run all unit tests (MUnit)
sbt core/test            # core unit tests only
sbt monorepo/test        # monorepo unit tests only
sbt scripted             # run all scripted integration tests

# sbt 2 / Scala 3 (version pinned in project/sbt2.version)
sbt -Dsbt.version=2.0.0-RC9 compile  # compile on sbt 2
sbt -Dsbt.version=2.0.0-RC9 test     # run unit tests on sbt 2
./bin/sbt2-clean test                # same sbt 2 test lane from a clean checkout of tracked files
./bin/sbt2-clean core/scripted       # core scripted tests on sbt 2
./bin/sbt2-clean monorepo/scripted   # monorepo scripted tests on sbt 2

# Formatting
sbt scalafmtAll          # format Scala sources
sbt scalafmtSbt          # format .sbt and project/*.scala build files
sbt scalafmtCheckAll     # verify Scala source formatting
sbt scalafmtSbtCheck     # verify sbt/build file formatting

Use ./bin/sbt2-clean ... for local sbt 2 verification when your checkout has generated IDE files such as project/metals.sbt or .bloop/ — those can interfere with sbt 2 compilation. CI runs on a clean checkout and uses plain sbt -Dsbt.version=2.0.0-RC9 ....

• sbt: 1.12.3 and 2.0.0-RC9
• Scala: 2.12 (sbt 1) / Scala 3 (sbt 2) — plugin compile targets, not constraints on your project's Scala version
• cats-effect: 3.7.0
• VCS: Git only

This project is licensed under the Apache License 2.0.

Ports sbt-release by the sbt organization onto cats-effect IO.

Developed with the assistance of Claude Code by Anthropic.