Monorepo Configuration

Optional for standalone package

Configure monorepo-specific behavior.

versionMode

Choose how versions are managed:

import { defineConfig } from 'relizy'

export default defineConfig({
  monorepo: {
    versionMode: 'selective', // 'unified' | 'selective' | 'independent'
  },
})

• unified: All packages share the same version
• selective: Only changed packages bumped (recommended)
• independent: Each package has its own version

Learn more: Version Modes

Independent mode commit messages

In independent mode, Relizy uses shorter release commit titles by default and moves the full package list into the commit body so you stay under commitlint header limits. See Commit Templates for placeholders and examples.

packages

Specify where packages are located:

export default defineConfig({
  monorepo: {
    packages: [
      'packages/*',
      'apps/*',
      'libs/*',
    ],
  },
})

ignored

Exclude packages by path, using the same glob syntax as packages. This is the recommended way to ignore packages, for consistency with packages.

export default defineConfig({
  monorepo: {
    packages: ['packages/*', 'shared-components/*'],
    ignored: [
      'shared-components/navigation', // a single package
      'packages/internal-*', // or a glob
    ],
  },
})

Ignored packages are excluded from bump, changelog, publish, provider-release and pr-comment.

Root bump & changelog (unified / selective)

In unified and selective mode the root version is derived from all commits in the repository. Commits whose changed files all live inside an ignored package are excluded from the root version bump and the root changelog.

This means a breaking change scoped to an ignored package no longer bumps the whole repository - as long as that change lives in its own commit. Keep ignored-package changes in dedicated commits (do not mix them with changes to released packages in the same commit), otherwise the commit still counts for the root.

ignorePackageNames

Deprecated

ignorePackageNames is deprecated in favor of ignored (path globs), for consistency with packages. Both options are still honored and merged together, so you can migrate incrementally.

Exclude specific packages by their package.json name:

export default defineConfig({
  monorepo: {
    ignorePackageNames: [
      'example-a',
      'docs',
      '@myorg/private',
    ],
  },
})

includePrivates

Include private packages (packages with "private": true in their package.json) in the release workflow, everywhere except publishing.

By default, private packages are excluded from every pipeline step. When this option is enabled, they are versioned like public ones:

• they get their own version bump and their own CHANGELOG.md
• their commits are included in the aggregated root changelog
• they get their own git tag (in independent mode)
• they get their own GitHub/GitLab release (in independent mode)
• they are listed in the packages table of PR comments

Private packages are never published to a registry: relizy publish always skips them, and PR comments never show install commands for them.

This is useful for monorepos that contain internal-only packages (apps, examples, private libraries) that still need versioning and release notes, and for fully private projects. See Private Projects & Apps.

export default defineConfig({
  monorepo: {
    versionMode: 'selective',
    packages: ['packages/*', 'apps/*'],
    includePrivates: true,
  },
})

You can also enable it ad-hoc from the CLI with the --include-private flag on relizy bump, relizy changelog, and relizy release.

NOTE

ignored / ignorePackageNames still take precedence. A private package listed in ignored (or ignorePackageNames) stays excluded even if includePrivates is true.

Complete Example

export default defineConfig({
  monorepo: {
    versionMode: 'selective',
    packages: ['packages/*', 'apps/*'],
    ignored: ['apps/docs'],
    includePrivates: false,
  },
})