Multiple Configurations

Use different configs for different workflows.

Why Multiple Configs?

Different release strategies for:

• Production vs staging
• Different package sets
• Different versioning modes
• Different registries

Creating Multiple Configs

Create config files with different names:

.
├── relizy.config.ts          # Default
├── relizy.production.config.ts
├── relizy.staging.config.ts
└── relizy.standalone.config.ts

Usage

CLI

# Use default config
relizy release

# Use production config
relizy release --config relizy.production

# Use staging config
relizy release --config relizy.staging

API

import { release } from 'relizy'

// Use custom config
await release({
  configName: 'relizy.staging',
  type: 'minor',
})

Example Configs

Production Config

// changelog.production.config.ts
export default defineConfig({
  monorepo: {
    versionMode: 'unified',
  },
  publish: {
    access: 'public',
    tag: 'latest',
  },
})

Staging Config

// changelog.staging.config.ts
export default defineConfig({
  monorepo: {
    versionMode: 'independent',
  },
  publish: {
    access: 'public',
    tag: 'beta',
  },
})

Standalone Package Config

// relizy.standalone.config.ts
export default defineConfig({
  // No monorepo settings
  publish: {
    access: 'public',
  },
})

Best Practices

1. Use descriptive names: production, staging, beta
2. Document usage: Add comments to each config
3. Share common settings: Extract to shared file
4. Version control: Commit all configs to git

Shared Configuration

Extract common settings:

// shared.config.ts
export const commonConfig = defineConfig({
  types: {
    feat: { title: '🚀 Features', semver: 'minor' },
    fix: { title: '🐛 Fixes', semver: 'patch' },
  },
})

// changelog.production.config.ts
import { commonConfig } from './shared.config'

export default defineConfig({
  ...commonConfig,
  publish: {
    tag: 'latest',
  },
})

// changelog.staging.config.ts
import { commonConfig } from './shared.config'

export default defineConfig({
  ...commonConfig,
  publish: {
    tag: 'beta',
  },
})