bump

Update version numbers in package.json files according to the release type and commits.

Usage

relizy bump [options]

What It Does

The bump command:

1. ✅ Calculates the new version
2. ✅ Updates package.json
3. ✅ Updates dependencies in monorepos
4. ❌ Does NOT create commits or tags
5. ❌ Does NOT generate changelogs

Options

Release Type

# Patch (1.0.0 → 1.0.1)
relizy bump --patch

# Minor (1.0.0 → 1.1.0)
relizy bump --minor

# Major (1.0.0 → 2.0.0)
relizy bump --major

--dry-run

Preview version changes:

relizy bump --minor --dry-run

--canary

Compute and write a canary version without publishing:

relizy bump --canary
# 1.2.3 → 1.3.0-canary.a3f4b2c.0

The canary version is based on the next version auto-detected from commits, with a canary suffix appended. Use --preid to customize the prerelease identifier:

relizy bump --canary --preid snapshot
# 1.2.3 → 1.3.0-snapshot.a3f4b2c.0

See the Canary Releases guide for full details.

--yes

Skip confirmations:

relizy bump --minor --yes

--include-private

Include private packages (packages with "private": true in their package.json) in the bump. By default, private packages are skipped.

relizy bump --minor --include-private

This is equivalent to setting monorepo.includePrivates: true in relizy.config.ts. Private packages participate in version bumping but are still excluded from publish and provider-release. See Monorepo Configuration — includePrivates.

Examples

Single Package

relizy bump --patch

# Before: "version": "1.0.0"
# After:  "version": "1.0.1"

Monorepo

relizy bump --minor

# packages/core: 1.0.0 → 1.1.0
# packages/ui: 1.0.0 → 1.1.0 (depends on core)

Preview Changes

relizy bump --major --dry-run

# Output:
# Packages to bump:
# ✓ @myorg/core: 1.5.0 → 2.0.0
# ✓ @myorg/ui: 1.5.0 → 2.0.0

Canary Version

relizy bump --canary

# Before: "version": "1.2.3"
# After:  "version": "1.3.0-canary.a3f4b2c.0"

See Also

• Canary Releases - Full guide on canary releases
• release - Full release workflow