uv-release-monorepo 0.18.1

Lazy monorepo wheel builder — only rebuilds what changed.

uv-release-monorepo

The missing CI release orchestrator for uv workspaces. Rebuilds only what changed, creates one GitHub release per package, handles version bumping.

Quick Start

uv tool install uv-release-monorepo
uvr init        # generate .github/workflows/release.yml
uvr release     # detect changes, show plan, dispatch to CI

Releasing

# Preview what would be released
uvr status

# Release to CI (default)
uvr release

# Release locally (pure-python packages only)
uvr release --where local

Release types

uvr release              # final: 1.0.1.dev0 → 1.0.1
uvr release --dev        # dev:   publish 1.0.1.dev0 as-is
uvr release --pre a      # alpha: 1.0.1.dev0 → 1.0.1a0
uvr release --pre rc     # rc:    1.0.1.dev0 → 1.0.1rc0
uvr release --post       # post:  1.0.1 → 1.0.1.post0

Skipping and reusing

uvr release --skip build                      # skip the build job
uvr release --skip-to release                 # skip everything before release
uvr release --skip build --reuse-run 12345    # reuse artifacts from run 12345

Managing runners

uvr runners                        # show all package runners
uvr runners my-pkg --add macos-14  # add a build runner
uvr runners my-pkg --clear         # reset to default (ubuntu-latest)

Installing from releases

uvr install myorg/myrepo/my-pkg           # latest release
uvr install myorg/myrepo/my-pkg@1.2.3     # specific version

Hooks

Customize the release pipeline with Python hooks. Subclass ReleaseHook and override the methods you need:

from uv_release_monorepo import ReleaseHook, ReleasePlan

class Hook(ReleaseHook):
    def post_plan(self, plan: ReleasePlan) -> ReleasePlan:
        data = plan.model_dump()
        data["deploy_env"] = "staging"
        return ReleasePlan.model_validate(data)

Configure in pyproject.toml:

[tool.uvr.hooks]
file = "uvr_hooks.py"          # default class: Hook
# or: file = "path/to/file.py:MyHook"

Or just drop a uvr_hooks.py with a Hook class at the workspace root — it's discovered automatically.

Hook points: pre_plan / post_plan (local), pre_build / post_build, pre_build_stage / post_build_stage, pre_build_package / post_build_package, pre_release / post_release, pre_finalize / post_finalize (CI).

How it works

uvr release scans your workspace, diffs each package against its last baseline tag, walks the dependency graph, and builds a plan containing every shell command needed for the release. It dispatches this plan to GitHub Actions, which runs eight jobs:

validate-plan → build → release → finalize

Hook jobs (pre-build, post-build, pre-release, post-release) are no-ops by default — edit release.yml directly to add tests, linting, PyPI publish, or notifications.

Documentation

• User Guide — setup, releasing, hooks, PyPI, skip/reuse, package filtering
• Under the Hood — change detection, dependency pinning, build matrix, workflow model