Social Media Configuration

Configure automatic release announcements on Twitter, Slack, and other social media platforms.

Overview

The social configuration allows you to automatically post release announcements to social media platforms when publishing new versions. Relizy currently supports Twitter (X) and Slack, with more platforms planned for the future.

Prerequisites

Social media integrations require platform-specific peer dependencies:

# For Twitter integration
pnpm add -D twitter-api-v2

# For Slack integration
pnpm add -D @slack/web-api

Configuration Structure

interface SocialConfig {
  twitter?: {
    enabled?: boolean
    onlyStable?: boolean
    template?: string
    credentials?: {
      apiKey?: string
      apiKeySecret?: string
      accessToken?: string
      accessTokenSecret?: string
    }
  }
  slack?: {
    enabled?: boolean
    onlyStable?: boolean
    channel?: string
    webhookUrl?: string
    template?: string
    credentials?: {
      token?: string
    }
    postMaxLength?: number
    noAuthors?: boolean
    noPackages?: boolean
  }
  changelogUrl?: string
}

twitter

Configure Twitter (X) integration for posting release announcements.

twitter.enabled

• Type: boolean
• Default: false

Enable or disable Twitter posting:

export default defineConfig({
  social: {
    twitter: {
      enabled: true,
    },
  },
})

twitter.onlyStable

• Type: boolean
• Default: true

Skip Twitter posting for prerelease versions (alpha, beta, rc, etc.). Only stable versions will be posted:

export default defineConfig({
  social: {
    twitter: {
      enabled: true,
      onlyStable: true, // Don't post beta/alpha releases
    },
  },
})

twitter.template

• Type: string
• Default: Auto-generated from version and changelog

Customize the tweet message template. Available variables:

• {{projectName}} - Project name
• {{version}} - Release version
• {{changelog}} - Changelog summary (truncated to fit Twitter's limit)
• {{releaseUrl}} - URL to GitHub/GitLab release
• {{changelogUrl}} - URL to full changelog (if configured)

export default defineConfig({
  social: {
    twitter: {
      enabled: true,
      template: '🚀 {{projectName}} v{{version}} is out!\n\n{{changelog}}\n\n{{releaseUrl}}',
    },
  },
})

twitter.postMaxLength

• Type: number
• Default: 280

Maximum length of the tweet. The message will be truncated if it exceeds this limit:

export default defineConfig({
  social: {
    twitter: {
      enabled: true,
      postMaxLength: 280,
    },
  },
})

twitter.credentials

• Type: TwitterCredentials
• Default: Read from environment variables

Twitter API credentials. If not provided, falls back to environment variables:

export default defineConfig({
  social: {
    twitter: {
      enabled: true,
      credentials: {
        apiKey: process.env.TWITTER_API_KEY,
        apiKeySecret: process.env.TWITTER_API_KEY_SECRET,
        accessToken: process.env.TWITTER_ACCESS_TOKEN,
        accessTokenSecret: process.env.TWITTER_ACCESS_TOKEN_SECRET,
      },
    },
  },
})

Environment Variables:

• TWITTER_API_KEY or RELIZY_TWITTER_API_KEY
• TWITTER_API_KEY_SECRET or RELIZY_TWITTER_API_KEY_SECRET
• TWITTER_ACCESS_TOKEN or RELIZY_TWITTER_ACCESS_TOKEN
• TWITTER_ACCESS_TOKEN_SECRET or RELIZY_TWITTER_ACCESS_TOKEN_SECRET

slack

Configure Slack integration for posting release notifications to channels.

slack.enabled

• Type: boolean
• Default: false

Enable or disable Slack posting:

export default defineConfig({
  social: {
    slack: {
      enabled: true,
    },
  },
})

slack.onlyStable

• Type: boolean
• Default: true

Skip Slack posting for prerelease versions (alpha, beta, rc, etc.). Only stable versions will be posted:

export default defineConfig({
  social: {
    slack: {
      enabled: true,
      onlyStable: true, // Don't post beta/alpha releases
    },
  },
})

slack.channel

• Type: string
• Required: Yes, in token mode. Ignored (with warning) in webhook mode — the channel is baked into the webhook URL.

Slack channel ID or name where release notifications will be posted:

export default defineConfig({
  social: {
    slack: {
      enabled: true,
      channel: '#releases', // Channel name
      // OR
      channel: 'C1234567890', // Channel ID
    },
  },
})

slack.webhookUrl

• Type: string
• Default: undefined

Slack Incoming Webhook URL. When set, takes priority over token-based authentication — the token and channel are ignored (with warnings) and @slack/web-api is not required.

export default defineConfig({
  social: {
    slack: {
      enabled: true,
      webhookUrl: process.env.SLACK_WEBHOOK_URL,
    },
  },
})

Environment Variables:

• RELIZY_SLACK_WEBHOOK_URL (takes priority)
• SLACK_WEBHOOK_URL

See the Slack Integration Guide for setup steps.

slack.template

• Type: string
• Default: Auto-generated from version and changelog

Customize the Slack message template. Available variables:

• {{projectName}} - Project name
• {{newVersion}} - Release version
• {{changelog}} - Changelog summary (truncated to postMaxLength)
• {{releaseUrl}} - URL to GitHub/GitLab release
• {{changelogUrl}} - URL to full changelog (if configured)
• {{contributors}} - Bullet list of contributor names (empty when noAuthors is active or none detected)

export default defineConfig({
  social: {
    slack: {
      enabled: true,
      webhookUrl: process.env.SLACK_WEBHOOK_URL,
      template: '🚀 *{{projectName}} v{{newVersion}}* is now available!\n\n{{changelog}}\n\n{{contributors}}\n\n<{{releaseUrl}}|View Release>',
    },
  },
})

slack.credentials

• Type: SlackCredentials
• Default: Read from environment variables

Slack Bot Token or User OAuth Token. Ignored in webhook mode. If not provided, falls back to environment variables:

export default defineConfig({
  social: {
    slack: {
      enabled: true,
      channel: '#releases',
      credentials: {
        token: process.env.SLACK_TOKEN,
      },
    },
  },
})

Environment Variables:

• SLACK_TOKEN or RELIZY_SLACK_TOKEN

Required Scopes:

• chat:write - Post messages to channels
• chat:write.public - Post to public channels (if using public channels)

slack.postMaxLength

• Type: number
• Default: 2500

Maximum number of characters for the changelog rendered in the Slack message. Slack's hard limit per section block is 3000 — the default leaves margin for mrkdwn conversion and formatting.

export default defineConfig({
  social: {
    slack: {
      enabled: true,
      webhookUrl: process.env.SLACK_WEBHOOK_URL,
      postMaxLength: 1500,
    },
  },
})

Lower this if you see invalid_payload errors from Slack.

slack.noAuthors

• Type: boolean
• Default: false

Hide the "❤️ Contributors" block in Slack messages. The global noAuthors setting takes priority — if it is true, contributors are always hidden regardless of this setting.

export default defineConfig({
  noAuthors: false, // global: show contributors everywhere (default)
  social: {
    slack: {
      enabled: true,
      webhookUrl: process.env.SLACK_WEBHOOK_URL,
      noAuthors: true, // hide contributors on Slack only
    },
  },
})

slack.noPackages

• Type: boolean
• Default: false

Hide the "📦 Packages" block (bulleted list of bumped packages with their before → after versions). In standalone (single-package) mode the block is skipped automatically.

export default defineConfig({
  social: {
    slack: {
      enabled: true,
      webhookUrl: process.env.SLACK_WEBHOOK_URL,
      noPackages: true, // hide the 📦 Packages block
    },
  },
})

The data shown in this block comes from the same internal helper (collectPackageBumps) that powers the PR comment package table, so the two views always stay in sync — only the rendering differs (GFM table vs Slack mrkdwn bullet list).

changelogUrl

• Type: string
• Optional

URL to your full changelog (e.g., hosted documentation). This URL will be included in social media posts:

export default defineConfig({
  social: {
    changelogUrl: 'https://example.com/changelog',
    twitter: {
      enabled: true,
    },
    slack: {
      enabled: true,
      channel: '#releases',
    },
  },
})

Complete Examples

Twitter Only

import { defineConfig } from 'relizy'

export default defineConfig({
  social: {
    twitter: {
      enabled: true,
      onlyStable: true,
      template: '🎉 {{projectName}} v{{version}} released!\n\n{{changelog}}\n\n📖 {{releaseUrl}}',
    },
    changelogUrl: 'https://myproject.com/changelog',
  },
})

Slack Only

import { defineConfig } from 'relizy'

export default defineConfig({
  social: {
    slack: {
      enabled: true,
      onlyStable: false, // Post all releases including prereleases
      channel: '#releases',
      template: '🚀 *{{projectName}} v{{version}}*\n\n{{changelog}}\n\n<{{releaseUrl}}|View on GitHub>',
    },
    changelogUrl: 'https://myproject.com/changelog',
  },
})

Both Twitter and Slack

import { defineConfig } from 'relizy'

export default defineConfig({
  social: {
    twitter: {
      enabled: true,
      onlyStable: true,
    },
    slack: {
      enabled: true,
      onlyStable: false,
      channel: '#releases',
    },
    changelogUrl: 'https://myproject.com/changelog',
  },
})

Using Environment Variables

import { defineConfig } from 'relizy'

export default defineConfig({
  social: {
    twitter: {
      enabled: process.env.ENABLE_TWITTER === 'true',
      credentials: {
        apiKey: process.env.TWITTER_API_KEY,
        apiKeySecret: process.env.TWITTER_API_KEY_SECRET,
        accessToken: process.env.TWITTER_ACCESS_TOKEN,
        accessTokenSecret: process.env.TWITTER_ACCESS_TOKEN_SECRET,
      },
    },
    slack: {
      enabled: process.env.ENABLE_SLACK === 'true',
      channel: process.env.SLACK_CHANNEL || '#releases',
      credentials: {
        token: process.env.SLACK_TOKEN,
      },
    },
  },
})

With Alternative Token Configuration

Relizy also supports the tokens configuration for credentials:

import { defineConfig } from 'relizy'

export default defineConfig({
  tokens: {
    twitter: {
      apiKey: process.env.TWITTER_API_KEY,
      apiKeySecret: process.env.TWITTER_API_KEY_SECRET,
      accessToken: process.env.TWITTER_ACCESS_TOKEN,
      accessTokenSecret: process.env.TWITTER_ACCESS_TOKEN_SECRET,
    },
    slack: process.env.SLACK_TOKEN,
  },
  social: {
    twitter: {
      enabled: true,
    },
    slack: {
      enabled: true,
      channel: '#releases',
    },
  },
})

Integration with Release Workflow

Social media posting is automatically triggered when you enable it in the release configuration:

import { defineConfig } from 'relizy'

export default defineConfig({
  release: {
    social: true, // Enable social posting in release workflow
  },
  social: {
    twitter: {
      enabled: true,
    },
    slack: {
      enabled: true,
      channel: '#releases',
    },
  },
})

Then run:

relizy release --patch

This will:

1. Bump version
2. Generate changelog
3. Create git commit and tag
4. Push to remote
5. Create GitHub/GitLab release
6. Publish to npm
7. Post to Twitter and Slack ✨

Standalone Usage

You can also post to social media independently using the social command:

relizy social --from v1.0.0 --to v1.1.0

See the CLI reference for more details.

See Also

• Twitter Integration Guide
• Slack Integration Guide
• Social Media Overview
• Release Configuration
• Hooks Configuration