Changelog

v1.8.0 (2026-10-20)

compare changes

🚀 Features

• Add the ai-sdk provider for AI release notes (f199679)

  New ai.provider: 'ai-sdk' option: release notes and social posts can be rewritten with any Vercel AI SDK model (OpenAI, Google, Mistral, ...) instead of Claude Code. Install ai and your provider package (e.g. pnpm add -D ai @ai-sdk/openai), then set ai.providers['ai-sdk'].model to a model such as openai('gpt-5-mini'), or to a Vercel AI Gateway model id such as 'openai/gpt-5-mini'. The credentials are read by the provider package (e.g. OPENAI_API_KEY). The optional reasoning option sets the reasoning effort of the models that support it.

🩹 Fixes

• Resolve the previous release from the versions of the release tags (d18543c)

  When a package was released independently in the same monorepo (e.g. a selective config plus an independent config), its name@version tag could become the start of the next release range, and the commits made before it were lost from the bump and the changelog. The previous release is now the release tag with the highest version up to the current version, instead of the most recent tag. In unified, selective and standalone modes, the release tags follow templates.tagBody (or the v1.2.3 and 1.2.3 formats) and a package tag never matches. In independent mode, they are the name@version tags of the package. A hotfix of an older version or a release of a branch not merged yet is no longer picked either.

❤️ Contributors

• Favour Emeka (@favorodera)
• LouisMazel (@LouisMazel)

v1.7.0 (2026-10-10)

compare changes

🚀 Features

• Create GitHub and GitLab releases for private packages when includePrivates is enabled (02d7c47)

  Private packages versioned with monorepo.includePrivates: true now get their own GitHub or GitLab release in independent mode, next to their git tag. They are still never published to a registry.

🩹 Fixes

• Render a working compare link and title for new packages in the changelog (a1e6c03)

• Read commits of a new package created in the repository root commit (6700387)

• Hide install commands and the unknown version in PR comments when nothing is published (9ad58f1)

  The installation section is omitted when release.publish is false and never lists private packages. In independent mode, the global version line is replaced by the packages table, which also lists private packages when monorepo.includePrivates is enabled.

📖 Documentation

• docs: Document versioning private projects without publishing (a825dab)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.7.0-beta.0 (2026-10-10)

compare changes

🚀 Features

• Create GitHub and GitLab releases for private packages when includePrivates is enabled (02d7c47)

  Private packages versioned with monorepo.includePrivates: true now get their own GitHub or GitLab release in independent mode, next to their git tag. They are still never published to a registry.

🩹 Fixes

• Render a working compare link and title for new packages in the changelog (a1e6c03)

• Read commits of a new package created in the repository root commit (6700387)

• Hide install commands and the unknown version in PR comments when nothing is published (9ad58f1)

  The installation section is omitted when release.publish is false and never lists private packages. In independent mode, the global version line is replaced by the packages table, which also lists private packages when monorepo.includePrivates is enabled.

📖 Documentation

• docs: Document versioning private projects without publishing (a825dab)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.6.0 (2026-10-07)

compare changes

🚀 Features

• relizy: Guard releases against commits pushed during the release (812ee2c)

  relizy release now protects the release commit when the branch moves while the release runs:

  • When push and commit are enabled, the release stops before publishing if the upstream branch received new commits, and restores the release files.
  • The release fails right after the bump if one of its tags already exists, with the command to recover.
  • A push rejected as non-fast-forward is recovered by merging the upstream branch into the release commit, then pushing again.

🩹 Fixes

• relizy: Mention rejected pushes in orphan tag and already published errors (ba3592a)

📖 Documentation

• docs: Document the release branch safety guards (e504b9e)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.5.1 (2026-10-06)

compare changes

🩹 Fixes

• Sort canary versions below every prerelease and stable release (cf939c9)

  Canary versions now use the {nextVersion}-0.{preid}-{sha} format (e.g. 5.0.0-0.canary-a3f4b2c instead of 5.0.0-canary.a3f4b2c.0). They no longer match semver ranges like ^5.0.0-beta.0 and are never suggested by pnpm outdated, pnpm update or Renovate. Install a canary by pinning its exact version or using the canary dist-tag.

• Keep co-author trailers and changed files of squash-merged commits (45e0d78)

  Commits whose body contains a ---- line, like the --------- GitHub adds before Co-authored-by: trailers when squash merging, lost their trailers and their changed files. In a monorepo they could be left out of a package changelog and bump. Commit subjects containing | are no longer truncated.

• Credit co-authors in the changelog contributors (caed2da)

  The contributors section now lists the co-authors read from Co-authored-by: trailers, so contributors of a squash-merged pull request are credited.

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.5.0 (2026-09-25)

compare changes

🚀 Features

• Support publishing to multiple registries (#113)

  • refactor(relizy): use deep imports for @maz-ui/utils helpers Closes #100, #105
  • feat: support publishing to multiple registries (#112)
  • feat(relizy): support publishing to multiple registries
  • test(relizy): add per-registry OTP caching coverage
  • feat(relizy): allow excluding the default registry per package
  • fix(relizy): normalize registry URLs before deduplication and OTP caching
  • fix(relizy): scope the publish safety check to registries actually needed by the release
  • refactor(relizy): rename RegistryTarget.packages to packageFilter

  ---

• Skip or clearly report already-published versions on publish (1442386)

  Add publish.skipExistingVersions (and the --skip-existing-versions flag on publish and release) to make re-running a release idempotent: packages whose version already exists on the registry are skipped, and only what is still missing gets published. When enabled, Relizy checks each package before publishing by querying the registry. This relies on the standard registry metadata endpoint that every npm-compatible registry implements, so it does not depend on the wording of any error message. The check works for every package manager: npm/pnpm use the view command (reusing your .npmrc auth), and yarn/bun fall back to a direct HTTPS request to the same endpoint. When the option is disabled (the default), an already-published version still fails the release, but with a clear message pointing to the option instead of the raw registry error. Especially useful for canary reruns on the same commit, where the version is regenerated identically.

• relizy: Add bump.capZeroMajor option to control 0.x graduation (de74327)

  By default relizy caps commit-detected major bumps to minor while the current version is in the 0.x.y range (semver §4), so a breaking change never graduates a 0.x package to 1.0.0 automatically. bump.capZeroMajor: false opts out: a breaking commit then bumps 0.x.y straight to 1.0.0, useful for a production-ready 0.x package released via CI without passing --major. It only affects commit-based detection (explicit CLI release types are never capped) and is a no-op once the package is 1.x. Defaults to true, so existing behavior is unchanged. No breaking change.

🩹 Fixes

• Aggregate per-package changelog for social posts in independent mode (#114)

• Omit implicit default registry when only registries is configured (3ee4a1c)

  You can now list every publish target in registries without setting a top-level registry. When no default registry is configured, Relizy no longer adds an implicit target pointing at the ambient .npmrc registry, so packages are published only to the registries you declare. Setting neither registry nor registries still falls back to the .npmrc-resolved registry, and a package matched by no registries entry falls back to it too.

• Authenticate and publish through .npmrc for pnpm 10+ compatibility (72876ad)

  The auth token (and, for scoped packages, the matching @scope:registry) is now written to .npmrc for the duration of each publish/whoami instead of being passed as CLI flags, which the pnpm 10+ parser rejects. Authentication and multi-registry publishing now behave identically on npm, pnpm (every version) and bun; your .npmrc is preserved and restored, and left untouched when no token/registry is configured. Yarn is not covered (set its auth in .yarnrc.yml). Scoped packages are now published to their configured registry instead of the one the ambient .npmrc points at, and additional registries without their own tag inherit the global publish tag, so a canary release keeps its tag on every registry.

• Base release announcements on the previous stable version (9647125)

  Release announcements (Slack messages and PR comments) now compare against the previous stable version instead of the last prerelease. A graduation is shown as 6.15.0 → 6.16.0 instead of 6.16.0-beta.5 → 6.16.0, matching the changelog. Prereleases are unaffected.

• relizy: Honor ignored packages in root bump and changelog (50147a0)

  In unified/selective mode the root version and changelog aggregated every commit, so a breaking change scoped to an ignored package (typically one released independently) bumped the whole repository. ignorePackageNames only removed the package from the published set, not from the root aggregation. Root commits are now filtered: a commit whose changed files all live inside an ignored package is excluded from the root version bump and the root changelog. Commits that mix ignored and released packages still count. Also add monorepo.ignored (path globs, same syntax as packages) as the recommended, path-based replacement for ignorePackageNames, which is now deprecated. Both options are honored and merged, so migration is incremental. No breaking change.

💅 Refactors

• Relocate tryPostPrComment and extract the release summary builder (3c700fa)

📖 Documentation

• Document listing every registry without a default (f0239a1)

📦 Build

• Upgrade dependencies (#116)

  • build: upgrade dependencies minor
  • build: upgrade vitest

• deps: Upgrade minor and patch dependencies (ce973e5)

• deps: Upgrade typescript to v6 (416f69a)

• deps: Upgrade @slack/web-api to v8 (3695ac2)

• deps: Upgrade vitepress to v2.0.0-alpha.20 (256dbf2)

• deps: Upgrade maz-ui deps (6dc947e)

🧪 Tests

• relizy: Keep isVersionPublished tests hermetic from registry token env (82ea63c)

❤️ Contributors

• LouisMazel (@LouisMazel)
• Mazel (@LouisMazel)

v1.5.0-beta.4 (2026-09-22)

compare changes

🚀 Features

• relizy: Add bump.capZeroMajor option to control 0.x graduation (de74327)

  By default relizy caps commit-detected major bumps to minor while the current version is in the 0.x.y range (semver §4), so a breaking change never graduates a 0.x package to 1.0.0 automatically. bump.capZeroMajor: false opts out: a breaking commit then bumps 0.x.y straight to 1.0.0, useful for a production-ready 0.x package released via CI without passing --major. It only affects commit-based detection (explicit CLI release types are never capped) and is a no-op once the package is 1.x. Defaults to true, so existing behavior is unchanged. No breaking change.

🩹 Fixes

• relizy: Honor ignored packages in root bump and changelog (50147a0)

  In unified/selective mode the root version and changelog aggregated every commit, so a breaking change scoped to an ignored package (typically one released independently) bumped the whole repository. ignorePackageNames only removed the package from the published set, not from the root aggregation. Root commits are now filtered: a commit whose changed files all live inside an ignored package is excluded from the root version bump and the root changelog. Commits that mix ignored and released packages still count. Also add monorepo.ignored (path globs, same syntax as packages) as the recommended, path-based replacement for ignorePackageNames, which is now deprecated. Both options are honored and merged, so migration is incremental. No breaking change.

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.5.0-beta.3 (2026-09-22)

compare changes

🚀 Features

• Skip or clearly report already-published versions on publish (1442386)

  Add publish.skipExistingVersions (and the --skip-existing-versions flag on publish and release) to make re-running a release idempotent: packages whose version already exists on the registry are skipped, and only what is still missing gets published. When enabled, Relizy checks each package before publishing by querying the registry. This relies on the standard registry metadata endpoint that every npm-compatible registry implements, so it does not depend on the wording of any error message. The check works for every package manager: npm/pnpm use the view command (reusing your .npmrc auth), and yarn/bun fall back to a direct HTTPS request to the same endpoint. When the option is disabled (the default), an already-published version still fails the release, but with a clear message pointing to the option instead of the raw registry error. Especially useful for canary reruns on the same commit, where the version is regenerated identically.

🩹 Fixes

• Base release announcements on the previous stable version (9647125)

  Release announcements (Slack messages and PR comments) now compare against the previous stable version instead of the last prerelease. A graduation is shown as 6.15.0 → 6.16.0 instead of 6.16.0-beta.5 → 6.16.0, matching the changelog. Prereleases are unaffected.

💅 Refactors

• Relocate tryPostPrComment and extract the release summary builder (3c700fa)

📦 Build

• deps: Upgrade minor and patch dependencies (ce973e5)
• deps: Upgrade typescript to v6 (416f69a)
• deps: Upgrade @slack/web-api to v8 (3695ac2)
• deps: Upgrade vitepress to v2.0.0-alpha.20 (256dbf2)
• deps: Upgrade maz-ui deps (6dc947e)

🧪 Tests

• relizy: Keep isVersionPublished tests hermetic from registry token env (82ea63c)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.5.0-beta.2 (2026-09-15)

compare changes

🩹 Fixes

• Authenticate and publish through .npmrc for pnpm 10+ compatibility (72876ad)

  The auth token (and, for scoped packages, the matching @scope:registry) is now written to .npmrc for the duration of each publish/whoami instead of being passed as CLI flags, which the pnpm 10+ parser rejects. Authentication and multi-registry publishing now behave identically on npm, pnpm (every version) and bun; your .npmrc is preserved and restored, and left untouched when no token/registry is configured. Yarn is not covered (set its auth in .yarnrc.yml). Scoped packages are now published to their configured registry instead of the one the ambient .npmrc points at, and additional registries without their own tag inherit the global publish tag, so a canary release keeps its tag on every registry.

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.5.0-beta.1 (2026-09-14)

compare changes

🩹 Fixes

• Omit implicit default registry when only registries is configured (3ee4a1c)

  You can now list every publish target in registries without setting a top-level registry. When no default registry is configured, Relizy no longer adds an implicit target pointing at the ambient .npmrc registry, so packages are published only to the registries you declare. Setting neither registry nor registries still falls back to the .npmrc-resolved registry, and a package matched by no registries entry falls back to it too.

📖 Documentation

• Document listing every registry without a default (f0239a1)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.5.0-beta.0 (2026-09-14)

compare changes

🚀 Features

• Support publishing to multiple registries (#113)

  • refactor(relizy): use deep imports for @maz-ui/utils helpers Closes #100, #105
  • feat: support publishing to multiple registries (#112)
  • feat(relizy): support publishing to multiple registries
  • test(relizy): add per-registry OTP caching coverage
  • feat(relizy): allow excluding the default registry per package
  • fix(relizy): normalize registry URLs before deduplication and OTP caching
  • fix(relizy): scope the publish safety check to registries actually needed by the release
  • refactor(relizy): rename RegistryTarget.packages to packageFilter

  ---

🩹 Fixes

• Aggregate per-package changelog for social posts in independent mode (#114)

📦 Build

• Upgrade dependencies (#116)
  • build: upgrade dependencies minor
  • build: upgrade vitest

❤️ Contributors

• Mazel (@LouisMazel)

v1.4.9 (2026-06-21)

compare changes

💅 Refactors

• relizy: Use deep imports for @maz-ui/utils helpers (#106)

  Closes #100, #105

❤️ Contributors

• Mazel (@LouisMazel)

v1.4.8 (2026-06-10)

compare changes

🩹 Fixes

• relizy: Include title-only commit types in changelog and release outputs (cb3dc6a)

  Commits whose configured type defines a title without a semver (e.g. docs: { title: '📖 Documentation' }) now appear in the CHANGELOG, GitHub/GitLab release notes, and Slack/Twitter posts. Such types still do not trigger a version bump — only types with a semver field do. Set the type to false to exclude it from both the changelog and the bump.

• Detect and recover from rewritten (orphaned) release tags (b4d6478)

  When a branch is rebased after a release, its tag points to a commit that is no longer in the history. The changelog then spanned everything since the last stable release (with duplicated commits) and bumped every package. Relizy now detects this and uses the right commit range, while leaving the tag name in the changelog untouched. In CI / non-interactive it auto-corrects for the run and warns; in a TTY it prompts. No commit is ever rewritten and nothing is mutated in dry-run.

  New config options

  export default defineConfig({
    // Enabled by default. Set to false to opt out.
    detectRewrittenTags: true,
    // Override the auto behaviour (prompt on TTY, ephemeral on CI):
    // 'prompt' | 'ephemeral' | 'rebind' | 'error'
    onRewrittenTag: 'ephemeral',
  })

• Redact secrets in logs to prevent token leakage (d2d9ed9)

  Tokens (npm, GitHub and others) could appear in clear text in Relizy's debug logs. They are now hidden, so sharing your logs no longer risks exposing your secrets.

• Prevent release hang on registry auth safety check (52cc132)

  registry authentication when the registry did not respond. It now stops after a short delay and shows a clear error instead of hanging. You can adjust the delay with publish.safetyCheckTimeout (15s by default) or skip the check with --no-safety-check.

• Honor the registry from .npmrc instead of forcing the public one (345f09b)

  Relizy always targeted the public npm registry for the authentication check and publishing, ignoring a custom registry set in your .npmrc (for example a corporate proxy). On networks where the public registry is only reachable through that proxy, this caused the registry check to hang. When publish.registry is not set, Relizy now resolves the registry from your npm config, so a proxy or private registry configured in .npmrc is respected. Set publish.registry only to force a specific registry.

• Keep a recognizable extract when masking secrets in logs (216f5f8)

  Masked secrets in the resolved-config debug output now keep their first and last few characters (e.g. npm_***2Hwk) instead of being fully replaced by [redacted], so you can still tell which token is which without exposing it. Secrets shorter than 16 characters are still masked entirely.

📦 Build

• Upgrade maz-ui dependencies (d827532)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.8-beta.1 (2026-06-10)

compare changes

🩹 Fixes

• Keep a recognizable extract when masking secrets in logs (216f5f8)

  Masked secrets in the resolved-config debug output now keep their first and last few characters (e.g. npm_***2Hwk) instead of being fully replaced by [redacted], so you can still tell which token is which without exposing it. Secrets shorter than 16 characters are still masked entirely.

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.8-beta.0 (2026-06-10)

compare changes

🩹 Fixes

• relizy: Include title-only commit types in changelog and release outputs (cb3dc6a)

  Commits whose configured type defines a title without a semver (e.g. docs: { title: '📖 Documentation' }) now appear in the CHANGELOG, GitHub/GitLab release notes, and Slack/Twitter posts. Such types still do not trigger a version bump — only types with a semver field do. Set the type to false to exclude it from both the changelog and the bump.

• Detect and recover from rewritten (orphaned) release tags (b4d6478)

  When a branch is rebased after a release, its tag points to a commit that is no longer in the history. The changelog then spanned everything since the last stable release (with duplicated commits) and bumped every package. Relizy now detects this and uses the right commit range, while leaving the tag name in the changelog untouched. In CI / non-interactive it auto-corrects for the run and warns; in a TTY it prompts. No commit is ever rewritten and nothing is mutated in dry-run.

  New config options

  export default defineConfig({
    // Enabled by default. Set to false to opt out.
    detectRewrittenTags: true,
    // Override the auto behaviour (prompt on TTY, ephemeral on CI):
    // 'prompt' | 'ephemeral' | 'rebind' | 'error'
    onRewrittenTag: 'ephemeral',
  })

• Redact secrets in logs to prevent token leakage (d2d9ed9)

  Tokens (npm, GitHub and others) could appear in clear text in Relizy's debug logs. They are now hidden, so sharing your logs no longer risks exposing your secrets.

• Prevent release hang on registry auth safety check (52cc132)

  registry authentication when the registry did not respond. It now stops after a short delay and shows a clear error instead of hanging. You can adjust the delay with publish.safetyCheckTimeout (15s by default) or skip the check with --no-safety-check.

• Honor the registry from .npmrc instead of forcing the public one (345f09b)

  Relizy always targeted the public npm registry for the authentication check and publishing, ignoring a custom registry set in your .npmrc (for example a corporate proxy). On networks where the public registry is only reachable through that proxy, this caused the registry check to hang. When publish.registry is not set, Relizy now resolves the registry from your npm config, so a proxy or private registry configured in .npmrc is respected. Set publish.registry only to force a specific registry.

📦 Build

• Upgrade maz-ui dependencies (d827532)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.7 (2026-06-09)

compare changes

🩹 Fixes

• Detect and recover from rewritten (orphaned) release tags (3000559)

  When a branch is rebased after a release, its tag points to a commit that is no longer in the history. The changelog then spanned everything since the last stable release (with duplicated commits) and bumped every package. Relizy now detects this and uses the right commit range, while leaving the tag name in the changelog untouched. In CI / non-interactive it auto-corrects for the run and warns; in a TTY it prompts. No commit is ever rewritten and nothing is mutated in dry-run.

  New config options

  export default defineConfig({
    // Enabled by default. Set to false to opt out.
    detectRewrittenTags: true,
    // Override the auto behaviour (prompt on TTY, ephemeral on CI):
    // 'prompt' | 'ephemeral' | 'rebind' | 'error'
    onRewrittenTag: 'ephemeral',
  })

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.6 (2026-05-29)

compare changes

🩹 Fixes

• relizy: Include title-only commit types in changelog and release outputs (b487aef)

  Commits whose configured type defines a title without a semver (e.g. docs: { title: '📖 Documentation' }) now appear in the CHANGELOG, GitHub/GitLab release notes, and Slack/Twitter posts. Such types still do not trigger a version bump — only types with a semver field do. Set the type to false to exclude it from both the changelog and the bump.

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.5 (2026-05-12)

compare changes

🩹 Fixes

• Fall back to last prerelease tag when no stable tag exists (8f8fce0)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.4 (2026-05-12)

compare changes

🩹 Fixes

• Use bumped version during npm/pnpm dry-run publish (bde2272)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.3 (2026-05-05)

compare changes

🩹 Fixes

• relizy: Prevent ENOBUFS for new sub-packages in unified/selective mode (f9fcc87)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.2 (2026-05-04)

compare changes

🩹 Fixes

• relizy: Bump all packages in unified mode regardless of commits (919705e)

  Fixes: #81

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.1 (2026-04-24)

compare changes

🩹 Fixes

• relizy: Skip AI safety check when social platform is disabled (6a69084)

  AI social credentials are no longer required when ai.social.<platform>.enabled is true but the matching social.<platform>.enabled is false or unset.

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.0 (2026-04-22)

compare changes

🚀 Features

• relizy: Add Slack webhook support, contributors block, configurable truncation (962603a)

  Slack integration now supports two transports: Bot Token (existing) and Incoming Webhook URL (new). When both are configured, the webhook takes priority and @slack/web-api is not required at all. A contributors block is auto-appended (names only, no emails, no GitHub handles) respecting the global noAuthors gate and an optional Slack-specific override. The hardcoded 500-char truncation is now configurable via postMaxLength (default 2500). No breaking changes — existing token+channel configs keep working. Example (webhook mode, simplest setup):

  import { defineConfig } from 'relizy'
  
  export default defineConfig({
    social: {
      slack: {
        enabled: true,
        webhookUrl: process.env.SLACK_WEBHOOK_URL,
        // postMaxLength: 2500   // optional, default 2500
        // noAuthors: false      // optional, hide contributors on Slack only
      },
    },
  })

• relizy: Add package list to slack release messages (7958aac)

  Slack release messages now include a 📦 Packages block listing every bumped package with its before → after version. Disable it with social.slack.noPackages: true:

  import { defineConfig } from 'relizy'
  
  export default defineConfig({
    social: {
      slack: {
        enabled: true,
        webhookUrl: process.env.SLACK_WEBHOOK_URL,
        noPackages: true,
      },
    },
  })

🩹 Fixes

• relizy: Include root-only commits in root package changelog (2aeaf27)

📦 Build

• Upgrade dependencies (ada24b0)

💄 Styles

• relizy: Bold package names in slack release messages (2f72640)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.0-beta.1 (2026-04-22)

compare changes

🚀 Features

• relizy: Add package list to slack release messages (333ff34)

  Slack release messages now include a 📦 Packages block listing every bumped package with its before → after version. Disable it with social.slack.noPackages: true:

  import { defineConfig } from 'relizy'
  
  export default defineConfig({
    social: {
      slack: {
        enabled: true,
        webhookUrl: process.env.SLACK_WEBHOOK_URL,
        noPackages: true,
      },
    },
  })

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.4.0-beta.0 (2026-04-22)

compare changes

🚀 Features

• relizy: Add Slack webhook support, contributors block, configurable truncation (6101168)

  Slack integration now supports two transports: Bot Token (existing) and Incoming Webhook URL (new). When both are configured, the webhook takes priority and @slack/web-api is not required at all. A contributors block is auto-appended (names only, no emails, no GitHub handles) respecting the global noAuthors gate and an optional Slack-specific override. The hardcoded 500-char truncation is now configurable via postMaxLength (default 2500). No breaking changes — existing token+channel configs keep working. Example (webhook mode, simplest setup):

  import { defineConfig } from 'relizy'
  
  export default defineConfig({
    social: {
      slack: {
        enabled: true,
        webhookUrl: process.env.SLACK_WEBHOOK_URL,
        // postMaxLength: 2500   // optional, default 2500
        // noAuthors: false      // optional, hide contributors on Slack only
      },
    },
  })

📦 Build

• Upgrade dependencies (a31a8cc)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.3.3 (2026-04-16)

compare changes

💅 Refactors

• Improve AI prompts for social and provider release posts (b169432)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.3.2 (2026-04-16)

compare changes

🩹 Fixes

• Prevent defu deep merge from overriding user-defined commit types (aabf96b)

  User-defined types entries were deep-merged with defaults by defu. Omitted properties like semver were filled from defaults, triggering unwanted version bumps (e.g. docs without semver got semver: 'patch').

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.3.1 (2026-04-16)

compare changes

📖 Documentation

• Update changelog (f82f43f)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.3.0 (2026-04-15)

compare changes

🚀 Features

• relizy: Support private packages in bump and changelog (c08ab50)

  Add a new monorepo.includePrivates option that lets internal, non-published packages participate in versioning and changelog generation. Private packages get bumped alongside public ones, receive their own CHANGELOG.md, and their commits land in the aggregated root changelog. They remain safely excluded from publish, provider-release, and pr-comment — versioned and documented, never pushed to a registry or announced.

  Why

  Monorepos often contain internal apps, examples, or private libraries that still need proper version tracking and changelog history without ever being published. Until now, relizy filtered those packages out of every pipeline step. With includePrivates, you get full versioning and changelog coverage for your private packages while keeping them out of the publish flow.

  Usage

  Enable it in relizy.config.ts:

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

  Or from the CLI on bump, changelog, or release:

  relizy release --minor --include-private

  Notes

  • Opt-in: default behavior is unchanged.
  • ignorePackageNames still takes precedence over includePrivates.
  • The bump confirmation prompt marks private packages with a 🔒 badge.
  • publish, provider-release, and pr-comment always ignore private packages — this is a safety guarantee, not a toggle.

• Smart prerelease base version recalculation (8eefe31)

  When in a prerelease cycle, Relizy now analyzes conventional commits to determine if the base version should increase. Previously, prerelease bumps always incremented the counter (e.g. 1.2.2-beta.0 → 1.2.2-beta.1) regardless of commit types. Now, if a feat commit is pushed after a patch-based beta, the base version correctly bumps to the next minor (e.g. 1.2.2-beta.1 → 1.3.0-beta.0). Similarly, a breaking change bumps to the next major (e.g. 1.3.0-beta.1 → 2.0.0-beta.0). The base version only goes up, never down — a fix after a minor-level beta simply increments the counter.

• Customizable release commit message and body + smart defaults for independent (ac2c9fc)

• AI-enhanced release notes and social posts (5f461f3)

  Rewrite GitHub/GitLab release bodies and Twitter/Slack posts with Claude via the optional @yoloship/claude-sdk integration. Opt-in per target. The raw changelog stays the source of truth — AI never touches the compare link, contributors, or PR/issue references.

  Usage

  // relizy.config.ts
  export default defineConfig({
    ai: {
      providerRelease: { enabled: true },
      social: {
        twitter: { enabled: true },
        slack: { enabled: true },
      },
    },
  })

  Set ANTHROPIC_API_KEY (or CLAUDE_CODE_OAUTH_TOKEN) and install the SDK: pnpm add -D @yoloship/claude-sdk. Toggle at runtime with --ai / --no-ai on release, provider-release, and social. Defaults to Claude Haiku. Fails safely (fallback: 'raw') and preserves the release on AI errors. Full guide: https://relizy.dev/guide/ai-changelog

🩹 Fixes

• repo: Normalize path separators to POSIX before commit body matching (0253f7e)

  On Windows, path.relative() returns backslash-separated paths (e.g. packages\admin) while git log --name-status always outputs forward slashes (e.g. packages/admin/src/main.ts). The String.includes() check therefore always returned false on win32, causing every package's commit list to be empty in independent monorepo mode and relizy to report "No packages to bump, no relevant commits found". Fix both affected sites in isCommitOfTrackedPackages and getPackageCommits by normalizing the path.relative() result with .split(sep).join('/') before the includes comparison. Fixes #52

• relizy: Compute per-package canary versions in independent mode (a3fe0a5)

  Closes #51

• Rollback untracked files when publish fail (5555aa3)

• Respect semver 0.x convention on breaking changes (0fca747)

  Breaking changes on a 0.x.y version no longer bump the package to 1.0.0 automatically. They now bump the minor version instead, following the semver convention for initial development. What changes for you

  • A commit like feat!: rewrite api on version 0.5.2 now produces 0.6.0 (previously 1.0.0).
  • Same logic for prereleases: 0.5.2-beta.1 + breaking change → 0.6.0-beta.0.
  • Non-breaking commits are unchanged: feat still bumps the minor, fix still bumps the patch. Graduating to 1.0.0 is now an explicit choice When your API is ready to be declared stable, graduate to 1.0.0 by passing --major explicitly:

  relizy release --major

  This matches what established tools (changesets, semantic-release, release-please) already do, and what the semver spec recommends for packages still in their initial development phase. Fix: #29

• Detect missing claude CLI binary before spawn (9701f50)

  Previously, when the claude CLI was not on PATH, the Node child process emitted an unhandled error event and crashed the release mid-flight with spawn claude ENOENT. The Claude Code provider's safety check now probes the binary with spawnSync and throws an actionable error listing the install paths (npm, brew, script), so the failure surfaces early and points users to the fix. Also installs @anthropic-ai/claude-code in the beta release workflow, and documents the binary requirement in the Installation guide, Getting Started, AI-Enhanced Changelogs guide, and AI config reference.

📦 Build

• Upgrade dependencies (2a55929)
• Upgrade dependencies (bbc0e30)

❤️ Contributors

• LouisMazel (@LouisMazel)
• Ruan-cat (@ruan-cat)

v1.3.0-beta.4 (2026-04-15)

compare changes

🩹 Fixes

• Detect missing claude CLI binary before spawn (0a43432)

  Previously, when the claude CLI was not on PATH, the Node child process emitted an unhandled error event and crashed the release mid-flight with spawn claude ENOENT. The Claude Code provider's safety check now probes the binary with spawnSync and throws an actionable error listing the install paths (npm, brew, script), so the failure surfaces early and points users to the fix. Also installs @anthropic-ai/claude-code in the beta release workflow, and documents the binary requirement in the Installation guide, Getting Started, AI-Enhanced Changelogs guide, and AI config reference.

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.3.0-beta.3 (2026-04-15)

compare changes

🚀 Features

• AI-enhanced release notes and social posts (f46b2aa)

  Rewrite GitHub/GitLab release bodies and Twitter/Slack posts with Claude via the optional @yoloship/claude-sdk integration. Opt-in per target. The raw changelog stays the source of truth — AI never touches the compare link, contributors, or PR/issue references.

  Usage

  // relizy.config.ts
  export default defineConfig({
    ai: {
      providerRelease: { enabled: true },
      social: {
        twitter: { enabled: true },
        slack: { enabled: true },
      },
    },
  })

  Set ANTHROPIC_API_KEY (or CLAUDE_CODE_OAUTH_TOKEN) and install the SDK: pnpm add -D @yoloship/claude-sdk. Toggle at runtime with --ai / --no-ai on release, provider-release, and social. Defaults to Claude Haiku. Fails safely (fallback: 'raw') and preserves the release on AI errors. Full guide: https://relizy.dev/guide/ai-changelog

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.3.0-beta.2 (2026-04-14)

compare changes

🚀 Features

• Customizable release commit message and body + smart defaults for independent (3a164a5)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.3.0-beta.1 (2026-04-14)

compare changes

🚀 Features

• relizy: Support private packages in bump and changelog (d0f45a0)

  Add a new monorepo.includePrivates option that lets internal, non-published packages participate in versioning and changelog generation. Private packages get bumped alongside public ones, receive their own CHANGELOG.md, and their commits land in the aggregated root changelog. They remain safely excluded from publish, provider-release, and pr-comment — versioned and documented, never pushed to a registry or announced.

  Why

  Monorepos often contain internal apps, examples, or private libraries that still need proper version tracking and changelog history without ever being published. Until now, relizy filtered those packages out of every pipeline step. With includePrivates, you get full versioning and changelog coverage for your private packages while keeping them out of the publish flow.

  Usage

  Enable it in relizy.config.ts:

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

  Or from the CLI on bump, changelog, or release:

  relizy release --minor --include-private

  Notes

  • Opt-in: default behavior is unchanged.
  • ignorePackageNames still takes precedence over includePrivates.
  • The bump confirmation prompt marks private packages with a 🔒 badge.
  • publish, provider-release, and pr-comment always ignore private packages — this is a safety guarantee, not a toggle.

• relizy: Support private packages in bump and changelog (24a55ec)

  Add a new monorepo.includePrivates option that lets internal, non-published packages participate in versioning and changelog generation. Private packages get bumped alongside public ones, receive their own CHANGELOG.md, and their commits land in the aggregated root changelog. They remain safely excluded from publish, provider-release, and pr-comment — versioned and documented, never pushed to a registry or announced.

  Why

  Monorepos often contain internal apps, examples, or private libraries that still need proper version tracking and changelog history without ever being published. Until now, relizy filtered those packages out of every pipeline step. With includePrivates, you get full versioning and changelog coverage for your private packages while keeping them out of the publish flow.

  Usage

  Enable it in relizy.config.ts:

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

  Or from the CLI on bump, changelog, or release:

  relizy release --minor --include-private

  Notes

  • Opt-in: default behavior is unchanged.
  • ignorePackageNames still takes precedence over includePrivates.
  • The bump confirmation prompt marks private packages with a 🔒 badge.
  • publish, provider-release, and pr-comment always ignore private packages — this is a safety guarantee, not a toggle.

• Smart prerelease base version recalculation (fadb1df)

  When in a prerelease cycle, Relizy now analyzes conventional commits to determine if the base version should increase. Previously, prerelease bumps always incremented the counter (e.g. 1.2.2-beta.0 → 1.2.2-beta.1) regardless of commit types. Now, if a feat commit is pushed after a patch-based beta, the base version correctly bumps to the next minor (e.g. 1.2.2-beta.1 → 1.3.0-beta.0). Similarly, a breaking change bumps to the next major (e.g. 1.3.0-beta.1 → 2.0.0-beta.0). The base version only goes up, never down — a fix after a minor-level beta simply increments the counter.

• Smart prerelease base version recalculation (c518a14)

  When in a prerelease cycle, Relizy now analyzes conventional commits to determine if the base version should increase. Previously, prerelease bumps always incremented the counter (e.g. 1.2.2-beta.0 → 1.2.2-beta.1) regardless of commit types. Now, if a feat commit is pushed after a patch-based beta, the base version correctly bumps to the next minor (e.g. 1.2.2-beta.1 → 1.3.0-beta.0). Similarly, a breaking change bumps to the next major (e.g. 1.3.0-beta.1 → 2.0.0-beta.0). The base version only goes up, never down — a fix after a minor-level beta simply increments the counter.

🩹 Fixes

• repo: Normalize path separators to POSIX before commit body matching (59f2984)

  On Windows, path.relative() returns backslash-separated paths (e.g. packages\admin) while git log --name-status always outputs forward slashes (e.g. packages/admin/src/main.ts). The String.includes() check therefore always returned false on win32, causing every package's commit list to be empty in independent monorepo mode and relizy to report "No packages to bump, no relevant commits found". Fix both affected sites in isCommitOfTrackedPackages and getPackageCommits by normalizing the path.relative() result with .split(sep).join('/') before the includes comparison. Fixes #52

• repo: Normalize path separators to POSIX before commit body matching (5bd83d3)

  On Windows, path.relative() returns backslash-separated paths (e.g. packages\admin) while git log --name-status always outputs forward slashes (e.g. packages/admin/src/main.ts). The String.includes() check therefore always returned false on win32, causing every package's commit list to be empty in independent monorepo mode and relizy to report "No packages to bump, no relevant commits found". Fix both affected sites in isCommitOfTrackedPackages and getPackageCommits by normalizing the path.relative() result with .split(sep).join('/') before the includes comparison. Fixes #52 Co-authored-by: Cursor [email protected]

• relizy: Compute per-package canary versions in independent mode (b293295)

  Closes #51

• relizy: Compute per-package canary versions in independent mode (1e3df0d)

  Closes #51

• Rollback untracked files when publish fail (2fa73a2)

• Rollback untracked files when publish fail (3479f02)

• Respect semver 0.x convention on breaking changes (e3536e8)

  Breaking changes on a 0.x.y version no longer bump the package to 1.0.0 automatically. They now bump the minor version instead, following the semver convention for initial development. What changes for you

  • A commit like feat!: rewrite api on version 0.5.2 now produces 0.6.0 (previously 1.0.0).
  • Same logic for prereleases: 0.5.2-beta.1 + breaking change → 0.6.0-beta.0.
  • Non-breaking commits are unchanged: feat still bumps the minor, fix still bumps the patch. Graduating to 1.0.0 is now an explicit choice When your API is ready to be declared stable, graduate to 1.0.0 by passing --major explicitly:

  relizy release --major

  This matches what established tools (changesets, semantic-release, release-please) already do, and what the semver spec recommends for packages still in their initial development phase. Fix: #29

📦 Build

• Upgrade dependencies (1f6c0c1)
• Upgrade dependencies (0b0d65c)
• Upgrade dependencies (494b290)
• Upgrade dependencies (a9e82f3)

❤️ Contributors

• LouisMazel (@LouisMazel)
• Ruan-cat (@ruan-cat)

v1.3.0-beta.0 (2026-04-13)

compare changes

🚀 Features

• Smart prerelease base version recalculation (c518a14)

  When in a prerelease cycle, Relizy now analyzes conventional commits to determine if the base version should increase. Previously, prerelease bumps always incremented the counter (e.g. 1.2.2-beta.0 → 1.2.2-beta.1) regardless of commit types. Now, if a feat commit is pushed after a patch-based beta, the base version correctly bumps to the next minor (e.g. 1.2.2-beta.1 → 1.3.0-beta.0). Similarly, a breaking change bumps to the next major (e.g. 1.3.0-beta.1 → 2.0.0-beta.0). The base version only goes up, never down — a fix after a minor-level beta simply increments the counter.

🩹 Fixes

• Rollback untracked files when publish fail (3479f02)

📦 Build

• Upgrade dependencies (a9e82f3)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.2.2-beta.2 (2026-04-10)

compare changes

🚀 Features

• relizy: Support private packages in bump and changelog (24a55ec)

  Add a new monorepo.includePrivates option that lets internal, non-published packages participate in versioning and changelog generation. Private packages get bumped alongside public ones, receive their own CHANGELOG.md, and their commits land in the aggregated root changelog. They remain safely excluded from publish, provider-release, and pr-comment — versioned and documented, never pushed to a registry or announced.

  Why

  Monorepos often contain internal apps, examples, or private libraries that still need proper version tracking and changelog history without ever being published. Until now, relizy filtered those packages out of every pipeline step. With includePrivates, you get full versioning and changelog coverage for your private packages while keeping them out of the publish flow.

  Usage

  Enable it in relizy.config.ts:

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

  Or from the CLI on bump, changelog, or release:

  relizy release --minor --include-private

  Notes

  • Opt-in: default behavior is unchanged.
  • ignorePackageNames still takes precedence over includePrivates.
  • The bump confirmation prompt marks private packages with a 🔒 badge.
  • publish, provider-release, and pr-comment always ignore private packages — this is a safety guarantee, not a toggle.

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.2.2-beta.1 (2026-03-24)

compare changes

🩹 Fixes

• relizy: Compute per-package canary versions in independent mode (1e3df0d)

  Closes #51

📦 Build

• Upgrade dependencies (0b0d65c)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.2.2-beta.0 (2026-03-24)

compare changes

🩹 Fixes

• repo: Normalize path separators to POSIX before commit body matching (5bd83d3)

  On Windows, path.relative() returns backslash-separated paths (e.g. packages\admin) while git log --name-status always outputs forward slashes (e.g. packages/admin/src/main.ts). The String.includes() check therefore always returned false on win32, causing every package's commit list to be empty in independent monorepo mode and relizy to report "No packages to bump, no relevant commits found". Fix both affected sites in isCommitOfTrackedPackages and getPackageCommits by normalizing the path.relative() result with .split(sep).join('/') before the includes comparison. Fixes #52 Co-authored-by: Cursor [email protected]

❤️ Contributors

• Ruan-cat (@ruan-cat)

v1.2.1 (2026-03-19)

compare changes

🩹 Fixes

• relizy: Escape @ mentions in changelog to prevent unintended Twitter user tags (7222aec)

❤️ Contributors

• LouisMazel [email protected]

v1.2.0 (2026-03-14)

compare changes

🚀 Features

• Add stripBoldMarkers option to extractChangelogSummary (8badf30)

• Add changelogTitle template option (223026e)

  Customize changelog section titles via templates.changelogTitle in your config. Available variables: , , .

  export default defineConfig({
    templates: {
      changelogTitle: '{{newVersion}} - {{date}}',
    },
  })

💅 Refactors

• Add dry-run preview with logger.box for social and provider releases (a93e711)

📖 Documentation

• Document changelogTitle template and stripBoldMarkers (a760ecf)

📦 Build

• Upgrade dependencies (67b1f4f)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.0.1...v1.1.0

compare changes

🚀 Features

• Add PR/MR comment with release information (1d3a800)

  Automatically post a comment on your pull request or merge request after relizy release with release status, version transitions, package table, and install commands. Supports 3 statuses: ✅ success, ⏭️ no-release, ❌ failed.

  Highlights

  • Two modes: append (new comment each time) or update (finds and updates existing comment via hidden marker)
  • GitHub & GitLab support (including enterprise/self-hosted)
  • Auto-detection of PR/MR from current branch, or manual override with --pr-number
  • Standalone command: relizy pr-comment
  • Integrated in release workflow (enabled by default)

  Configuration

  // relizy.config.ts
  export default defineConfig({
    prComment: {
      mode: 'append', // or 'update'
    },
    release: {
      prComment: true, // enabled by default, set false to disable
    },
  })

  CLI

  # As part of release
  relizy release --patch
  # Standalone
  relizy pr-comment
  # Skip during release
  relizy release --patch --no-pr-comment
  # Override PR number (useful in CI)
  relizy release --patch --pr-number 42

• Add canary release mode (aaa49bf)

  Publish temporary test versions from any branch with --canary. Canary versions use the format {nextVersion}-{preid}.{sha}.0 (e.g., 1.3.0-canary.a3f4b2c.0). The next version is auto-detected from commits, then the canary suffix is appended.

  • Bumps all packages to a canary version
  • Publishes to npm with a canary dist-tag (or custom preid)
  • Posts a PR/MR comment with the canary version details
  • Skips changelog, git commit, git tag, git push, provider release, and social media posting

  relizy release --canary
  relizy release --canary --preid snapshot
  relizy release --canary --yes --pr-number 42
  relizy bump --canary

🩹 Fixes

• Prevent ENOBUFS error on new packages in independent mode (4aee6a3)

  New packages without tags now use the first commit that touched the package directory instead of the repository's first commit.

• Report PR comment post status accurately in release summary (df2fa1e)

  Propagate success/failure boolean through the entire posting chain so the summary shows "Failed" when needed.

💅 Refactors

• Show one install command per package in PR comments (f997136)

📖 Documentation

• docs: Add project name config in overview (cfe000e)
• Update config docs (5fc4513)

📦 Build

• Upgrade dependencies (0362261)
• Upgrade dependencies (2f86a38)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.1.0-beta.2...v1.1.0-beta.3

compare changes

🩹 Fixes

• Report PR comment post status accurately in release summary (080437c)

  Propagate success/failure boolean through the entire posting chain so the summary shows "Failed" when needed.

💅 Refactors

• Show one install command per package in PR comments (ebef38b)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.1.0-beta.1...v1.1.0-beta.2

compare changes

🚀 Features

• Add canary release mode (c01b812)

  Publish temporary test versions from any branch with --canary. Canary versions use the format {nextVersion}-{preid}.{sha}.0 (e.g., 1.3.0-canary.a3f4b2c.0). The next version is auto-detected from commits, then the canary suffix is appended.

  What it does

  • Bumps all packages to a canary version
  • Publishes to npm with a canary dist-tag (or custom preid)
  • Posts a PR/MR comment with the canary version details
  • Skips changelog, git commit, git tag, git push, provider release, and social media posting

  CLI

  # Canary release
  relizy release --canary
  # Custom preid
  relizy release --canary --preid snapshot
  # → 1.3.0-snapshot.a3f4b2c.0
  # In CI with PR comment
  relizy release --canary --yes --pr-number 42
  # Bump only (no publish)
  relizy bump --canary

• Add canary release mode (bdfae3d)

  Publish temporary test versions from any branch with --canary. Canary versions use the format {nextVersion}-{preid}.{sha}.0 (e.g., 1.3.0-canary.a3f4b2c.0). The next version is auto-detected from commits, then the canary suffix is appended.

  • Bumps all packages to a canary version
  • Publishes to npm with a canary dist-tag (or custom preid)
  • Posts a PR/MR comment with the canary version details
  • Skips changelog, git commit, git tag, git push, provider release, and social media posting

  relizy release --canary
  relizy release --canary --preid snapshot
  relizy release --canary --yes --pr-number 42
  relizy bump --canary

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.1.0-beta.0...v1.1.0-beta.1

compare changes

🚀 Features

• Add canary release mode (c01b812)

  Publish temporary test versions from any branch with --canary. Canary versions use the format {nextVersion}-{preid}.{sha}.0 (e.g., 1.3.0-canary.a3f4b2c.0). The next version is auto-detected from commits, then the canary suffix is appended.

  What it does

  • Bumps all packages to a canary version
  • Publishes to npm with a canary dist-tag (or custom preid)
  • Posts a PR/MR comment with the canary version details
  • Skips changelog, git commit, git tag, git push, provider release, and social media posting

  CLI

  # Canary release
  relizy release --canary
  # Custom preid
  relizy release --canary --preid snapshot
  # → 1.3.0-snapshot.a3f4b2c.0
  # In CI with PR comment
  relizy release --canary --yes --pr-number 42
  # Bump only (no publish)
  relizy bump --canary

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.0.2-beta.1...v1.1.0-beta.0

compare changes

🚀 Features

• Add PR/MR comment with release information (fefaa3b)

  Automatically post a comment on your pull request or merge request after relizy release with release status, version transitions, package table, and install commands. Supports 3 statuses: ✅ success, ⏭️ no-release, ❌ failed.

  Highlights

  • Two modes: append (new comment each time) or update (finds and updates existing comment via hidden marker)
  • GitHub & GitLab support (including enterprise/self-hosted)
  • Auto-detection of PR/MR from current branch, or manual override with --pr-number
  • Standalone command: relizy pr-comment
  • Integrated in release workflow (enabled by default)

  Configuration

  // relizy.config.ts
  export default defineConfig({
    prComment: {
      mode: 'append', // or 'update'
    },
    release: {
      prComment: true, // enabled by default, set false to disable
    },
  })

  CLI

  # As part of release
  relizy release --patch
  # Standalone
  relizy pr-comment
  # Skip during release
  relizy release --patch --no-pr-comment
  # Override PR number (useful in CI)
  relizy release --patch --pr-number 42

📦 Build

• Upgrade dependencies (0b00262)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.0.2-beta.0...v1.0.2-beta.1

compare changes

🚀 Features

• Add release PR comment (462147f)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.0.1...v1.0.2-beta.0

compare changes

🩹 Fixes

• Prevent ENOBUFS error on new packages in independent mode (fca172f)

  New packages without tags now use the first commit that touched the package directory instead of the repository's first commit.

📖 Documentation

• docs: Add project name config in overview (cfe000e)
• Update config docs (5fc4513)

📦 Build

• Upgrade dependencies (1ef5a67)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.0.0...v1.0.1

compare changes

💅 Refactors

• Add projectName config option (08ca6a5)

  Allows overriding the package name from root package.json for Twitter (X) and Slack posts. Use projectName in your config to customize the displayed name in social notifications.

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.3.0...v1.0.0

compare changes

🚀 Features

• Add automatic Twitter posting for releases (0e2062a)

  Add functionality to automatically post release announcements to Twitter when a new version is published.

  • New Twitter integration module (src/core/twitter.ts) with:
    • Twitter credentials management from environment variables
    • Tweet message formatting with customizable templates
    • Release URL generation for GitHub/GitLab
    • Changelog summary extraction
    • Smart truncation to fit Twitter's 280 character limit
  • Configuration support:
    • release.twitter option to enable/disable Twitter posting
    • templates.twitterMessage for custom tweet templates
    • Environment variables for Twitter API credentials:
      • TWITTER_API_KEY / RELIZY_TWITTER_API_KEY
      • TWITTER_API_SECRET / RELIZY_TWITTER_API_SECRET
      • TWITTER_ACCESS_TOKEN / RELIZY_TWITTER_ACCESS_TOKEN
      • TWITTER_ACCESS_TOKEN_SECRET / RELIZY_TWITTER_ACCESS_TOKEN_SECRET
  • CLI support:
    • --twitter flag for the release command to enable Twitter posting
    • Hooks support: before:twitter, success:twitter, error:twitter
  • Integration:
    • Added as Step 7/7 in the release workflow
    • Non-blocking: Twitter posting failures won't fail the release
    • Dry-run support for testing
  • Added twitter-api-v2 for Twitter API integration Enable Twitter posting with environment variables set: relizy release --twitter Or configure in relizy.config.ts: export default defineConfig({ release: { twitter: true } })

• Add option to skip Twitter posts for prerelease versions (d068175)

  Add twitterOnlyStable option to control whether prerelease versions (alpha, beta, rc, etc.) should be posted to Twitter.

  • New configuration option release.twitterOnlyStable (default: true)
    • When enabled, only stable versions will be posted to Twitter
    • Prerelease versions will be skipped automatically
  • CLI flag --no-twitter-only-stable to allow Twitter posts for prerelease versions when needed
  • Updated handleTwitterPost function to check if version is a prerelease before posting By default, Twitter posting is now limited to stable versions only. Users can override this with:
    • Config: release.twitterOnlyStable: false
    • CLI: --no-twitter-only-stable flag Stable release (v1.0.0): Will be posted to Twitter Prerelease (v1.0.0-beta.1): Will be skipped (unless configured)

• release: ⚠️ Add Slack integration to social media posting (5cb4fb6)

  BREAKING CHANGE: Add comprehensive Slack support to social command

  • Add SlackSocialConfig, SlackCredentials, SlackOptions types
  • Install @slack/web-api dependency for Slack Web API integration
  • Create src/core/slack.ts with Slack posting functionality
    • Support for rich blocks format (default) or custom templates
    • Automatic markdown to Slack mrkdwn conversion
    • Channel and token configuration with environment variable fallback
  • Create src/core/social-utils.ts for shared utilities
    • extractChangelogSummary() for changelog condensing
    • getReleaseUrl() for release URL generation
    • Shared between Twitter and Slack implementations
  • Add changelogUrl to SocialConfig for full changelog links
  • Update Twitter integration to support changelogUrl
  • Integrate Slack into social.ts with handleSlackPost()
    • Add safety checks for Slack credentials and channel
    • Support for before:slack, success:slack, error:slack hooks
    • Skip prerelease versions with onlyStable option
  • Add default Slack configuration and templates
  • Add 'slack' to HookStep type for hook support Features:
  • Post release announcements to any Slack workspace
  • Rich interactive messages with buttons (View Release, Full Changelog)
  • Configurable channel (supports both names and IDs)
  • Template support for custom message formatting
  • Smart changelog condensing with full changelog links
  • Dry-run support for testing

• release: Add partial Bitbucket support (b7f1d3c)

  Add Bitbucket as a supported Git provider with limited functionality. Bitbucket does not have a releases API like GitHub/GitLab, so releases are skipped for Bitbucket repositories. Changes:

  • Add 'bitbucket' to GitProvider type
  • Update detectGitProvider() to detect Bitbucket repositories
    • Checks for 'bitbucket.org' or 'bitbucket' in remote URL
  • Update getReleaseUrl() to generate Bitbucket tag URLs
    • Format: https://{domain}/{repo}/commits/tag/
  • Update providerReleaseSafetyCheck() to handle Bitbucket
    • Shows informative warning that releases are not supported
    • Allows other features (versioning, changelog, publishing, social) to work
  • Update providerRelease() to skip release creation for Bitbucket
    • Returns empty postedReleases array
    • Logs clear warning messages
    • Still triggers success hooks Bitbucket support includes: ✅ Git provider detection ✅ Tag URLs for social media posts ✅ Compare URLs in changelog (via changelogen 0.6.2+) ✅ Versioning, changelog generation ✅ NPM publishing ✅ Social media posting (Twitter/Slack) ❌ Release creation (not available in Bitbucket API) The compare URLs in changelogs are automatically handled by changelogen which supports Bitbucket format: /branches/compare/{tag2}..

• relizy: Add global tokens configuration for Twitter and Slack (0492d3c)

  Add centralized token management in the global config.tokens object, with priority system for credential resolution. Changes:

  • Create Tokens interface in types.ts with support for:
    • github: GitHub token
    • gitlab: GitLab token
    • twitter: Twitter API credentials (apiKey, apiSecret, accessToken, accessTokenSecret)
    • slack: Slack bot token
  • Update RelizyConfig to:
    • Omit 'tokens' from IChangelogConfig (avoid conflict)
    • Add tokens?: Tokens property
  • Update config.ts to populate tokens from environment variables:
    • twitter.apiKey: TWITTER_API_KEY or RELIZY_TWITTER_API_KEY
    • twitter.apiSecret: TWITTER_API_SECRET or RELIZY_TWITTER_API_SECRET
    • twitter.accessToken: TWITTER_ACCESS_TOKEN or RELIZY_TWITTER_ACCESS_TOKEN
    • twitter.accessTokenSecret: TWITTER_ACCESS_TOKEN_SECRET or RELIZY_TWITTER_ACCESS_TOKEN_SECRET
    • slack: SLACK_TOKEN or RELIZY_SLACK_TOKEN
  • Update getTwitterCredentials() to use priority system:
    1. social.twitter.credentials (specific config)
    2. config.tokens.twitter (global config)
    3. Environment variables (handled in config.ts)
  • Update getSlackToken() to use priority system:
    1. social.slack.credentials (specific config)
    2. config.tokens.slack (global config)
    3. Environment variables (handled in config.ts)
  • Update social.ts to pass both credential sources to helpers Benefits:
  • Centralized token management
  • Clear priority system (specific > global > env)
  • Consistent with GitHub/GitLab token pattern
  • Users can configure tokens once in config.tokens or per-platform in social.*
  • Better developer experience with multiple configuration options

• relizy: Add Codecov integration with optimal configuration (810b21c)

• docs: Add contributors section (38425bd)

• Improve error reporting for social and provider-release steps (6d85e7a)

  Social media and provider release failures are now non-blocking and provide detailed feedback in the final release summary. Changes:

  • Social command returns SocialResult with per-platform details
  • Provider-release returns errors in result instead of throwing
  • Release workflow displays detailed status in final log box Example output: Social media: 1 succeeded, 1 failed (slack) Provider release: Failed: Invalid token This allows releases to continue even if external services fail, while giving users full visibility into what succeeded or failed.

• safetyCheck is enable by default (aea2dec)

• Add config to choose the max length of the twitter post (7c98abb)

🩹 Fixes

• release: Add optional chaining for createdTags in success logger (aa7928b)

  • Fix TypeError when createdTags is undefined in tests
  • Use optional chaining (createdTags?.length) to safely access length
  • Change fallback text from 'No' to 'None' for clarity
  • Resolves 41 E2E test failures
  • Progress: 692/862 tests passing (80.3%)

• Remove postinstall script (ac8187a)

💅 Refactors

• Restructure social media configuration (064cefb)

  Refactor the social media posting configuration to be more modular and extensible for future platforms.

  • Removed twitter and twitterOnlyStable from ReleaseConfig
  • Added new release.social flag to enable all social media posting
  • Created new SocialConfig interface with platform-specific configs
  • Added social.twitter configuration section with:
    • enabled: Enable/disable Twitter posting
    • onlyStable: Skip prereleases (default: true)
    • messageTemplate: Custom tweet template
    • credentials: Optional Twitter API credentials (falls back to env vars)
  • More scalable architecture for adding new platforms (LinkedIn, Slack, Discord, etc.)
  • Cleaner separation of concerns
  • Platform-specific configuration
  • Credentials can be in config or environment variables Before: release: { twitter: true, twitterOnlyStable: true } After: release: { social: true }, social: { twitter: { enabled: true, onlyStable: true } }
  • Replaced --twitter flag with --social
  • Removed --no-twitter-only-stable flag (use config instead)
  • Created ResolvedTwitterCredentials type for type safety
  • Updated getTwitterCredentials to accept config credentials
  • Refactored handleTwitterPost to use new config structure
  • Updated release workflow step label to "social media"

• Create standalone social command (f3bdcd4)

  Create a dedicated social command that can be used independently or as part of the release workflow.

  • Created src/commands/social.ts with:
    • social() function - Main command implementation
    • socialSafetyCheck() - Validates social media credentials
    • handleTwitterPost() - Handles Twitter posting logic
    • Full changelog generation from git commits
  • Added new command: relizy social --from x.x.x --to x.x.x
  • Changed release flag from --social to --no-social
  • Default behavior: social posting is enabled (disable with --no-social)
  • Updated release.ts to call social() command instead of inline logic
  • Integrated socialSafetyCheck() in releaseSafetyCheck()
  • Removed handleTwitterPost from release.ts (moved to social.ts)
  • Changed release.social default from false to true
  • Social posting now enabled by default in release workflow
  • Use --no-social flag to disable during release
  • Added SocialOptions interface for command options
  • Added 'social' to HookStep type for hooks support
  • Modular: Social posting can be used independently
  • Reusable: Same logic in release and standalone command
  • Testable: Easier to test social posting in isolation
  • Extensible: Easy to add new social platforms
  • Safety: Validates credentials before attempting to post Standalone: relizy social --from v1.0.0 --to v1.1.0 In release workflow: relizy release # Social posting enabled by default relizy release --no-social # Disable social posting

• release: Use bumpResult fallback when postedReleases unavailable (f11e75f)

  • Add buildPostedReleasesFromBumpResult() to create releases from bump result
  • Implement priority system: postedReleases first, then bumpResult fallback
  • Handle independent, unified, and selective version modes
  • Add comprehensive logging with [social] and [social:twitter] prefixes
  • Ensure social posting works even when GitHub/GitLab releases are disabled This allows the social command to function independently of provider releases, making it more flexible and reliable in various release configurations.

• Put social dependencies in peerDependencies (b51c011)

• docs: Add social features to sidebar and navbar (424cf33)

• Social - improve format of twitter post (bea4991)

• Improve logs of safety check methods (3c25d6d)

• Improve logs of safety check methods (e0601d8)

• Improve social safety check Checking if twitter-api-v2 and/or @slack/web-api are installed if needed (d24c49c)

📖 Documentation

• Add social media integration documentation (266da58)

  • Simplified README.md with social media features
  • Added comprehensive social media guides (overview, Twitter, Slack)
  • Updated provider-release docs with Bitbucket limitations
  • Fixed release config documentation (providerRelease property)
  • Updated config overview with social tokens

• Add link to CONTRIBUTING.md in README PR guidelines (af862de)

• Add complete social media documentation and SEO metadata (9101672)

  • Create docs/src/config/social.md with detailed configuration reference
  • Create docs/src/api/social.md with API documentation and examples
  • Create docs/src/cli/social.md with CLI usage guide
  • Add SEO frontmatter metadata to slack-integration.md guide
  • Add SEO frontmatter metadata to social-media.md guide
  • Add SEO frontmatter metadata to twitter-integration.md guide
  • Document Twitter and Slack configuration options, credentials, templates
  • Include CI/CD integration examples for GitHub Actions and GitLab CI
  • Add troubleshooting sections and complete usage examples

📦 Build

• Upgrade dependencies (e2b07e8)

⚠️ Breaking Changes

• release: ⚠️ Add Slack integration to social media posting (5cb4fb6)

  BREAKING CHANGE: Add comprehensive Slack support to social command

  • Add SlackSocialConfig, SlackCredentials, SlackOptions types
  • Install @slack/web-api dependency for Slack Web API integration
  • Create src/core/slack.ts with Slack posting functionality
    • Support for rich blocks format (default) or custom templates
    • Automatic markdown to Slack mrkdwn conversion
    • Channel and token configuration with environment variable fallback
  • Create src/core/social-utils.ts for shared utilities
    • extractChangelogSummary() for changelog condensing
    • getReleaseUrl() for release URL generation
    • Shared between Twitter and Slack implementations
  • Add changelogUrl to SocialConfig for full changelog links
  • Update Twitter integration to support changelogUrl
  • Integrate Slack into social.ts with handleSlackPost()
    • Add safety checks for Slack credentials and channel
    • Support for before:slack, success:slack, error:slack hooks
    • Skip prerelease versions with onlyStable option
  • Add default Slack configuration and templates
  • Add 'slack' to HookStep type for hook support Features:
  • Post release announcements to any Slack workspace
  • Rich interactive messages with buttons (View Release, Full Changelog)
  • Configurable channel (supports both names and IDs)
  • Template support for custom message formatting
  • Smart changelog condensing with full changelog links
  • Dry-run support for testing

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.0.0-beta.2...v1.0.0-beta.3

compare changes

💅 Refactors

• Improve logs of safety check methods (0bb788a)

📦 Build

• Upgrade dependencies (5336e48)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.0.0-beta.1...v1.0.0-beta.2

compare changes

🚀 Features

• Add config to choose the max length of the twitter post (da73a00)

💅 Refactors

• Social - improve format of twitter post (1043d2a)

❤️ Contributors

• LouisMazel (@LouisMazel)

v1.0.0-beta.0...v1.0.0-beta.1

compare changes

🚀 Features

• safetyCheck is enable by default (075dc4e)

🩹 Fixes

• Remove postinstall script (ea98dff)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.3.0...v1.0.0-beta.0

compare changes

🚀 Features

• Add automatic Twitter posting for releases (684f92b)

  Add functionality to automatically post release announcements to Twitter when a new version is published.

  • New Twitter integration module (src/core/twitter.ts) with:
    • Twitter credentials management from environment variables
    • Tweet message formatting with customizable templates
    • Release URL generation for GitHub/GitLab
    • Changelog summary extraction
    • Smart truncation to fit Twitter's 280 character limit
  • Configuration support:
    • release.twitter option to enable/disable Twitter posting
    • templates.twitterMessage for custom tweet templates
    • Environment variables for Twitter API credentials:
      • TWITTER_API_KEY / RELIZY_TWITTER_API_KEY
      • TWITTER_API_SECRET / RELIZY_TWITTER_API_SECRET
      • TWITTER_ACCESS_TOKEN / RELIZY_TWITTER_ACCESS_TOKEN
      • TWITTER_ACCESS_TOKEN_SECRET / RELIZY_TWITTER_ACCESS_TOKEN_SECRET
  • CLI support:
    • --twitter flag for the release command to enable Twitter posting
    • Hooks support: before:twitter, success:twitter, error:twitter
  • Integration:
    • Added as Step 7/7 in the release workflow
    • Non-blocking: Twitter posting failures won't fail the release
    • Dry-run support for testing
  • Added twitter-api-v2 for Twitter API integration Enable Twitter posting with environment variables set: relizy release --twitter Or configure in relizy.config.ts: export default defineConfig({ release: { twitter: true } })

• Add option to skip Twitter posts for prerelease versions (e263972)

  Add twitterOnlyStable option to control whether prerelease versions (alpha, beta, rc, etc.) should be posted to Twitter.

  • New configuration option release.twitterOnlyStable (default: true)
    • When enabled, only stable versions will be posted to Twitter
    • Prerelease versions will be skipped automatically
  • CLI flag --no-twitter-only-stable to allow Twitter posts for prerelease versions when needed
  • Updated handleTwitterPost function to check if version is a prerelease before posting By default, Twitter posting is now limited to stable versions only. Users can override this with:
    • Config: release.twitterOnlyStable: false
    • CLI: --no-twitter-only-stable flag Stable release (v1.0.0): Will be posted to Twitter Prerelease (v1.0.0-beta.1): Will be skipped (unless configured)

• release: ⚠️ Add Slack integration to social media posting (7a32114)

  BREAKING CHANGE: Add comprehensive Slack support to social command

  • Add SlackSocialConfig, SlackCredentials, SlackOptions types
  • Install @slack/web-api dependency for Slack Web API integration
  • Create src/core/slack.ts with Slack posting functionality
    • Support for rich blocks format (default) or custom templates
    • Automatic markdown to Slack mrkdwn conversion
    • Channel and token configuration with environment variable fallback
  • Create src/core/social-utils.ts for shared utilities
    • extractChangelogSummary() for changelog condensing
    • getReleaseUrl() for release URL generation
    • Shared between Twitter and Slack implementations
  • Add changelogUrl to SocialConfig for full changelog links
  • Update Twitter integration to support changelogUrl
  • Integrate Slack into social.ts with handleSlackPost()
    • Add safety checks for Slack credentials and channel
    • Support for before:slack, success:slack, error:slack hooks
    • Skip prerelease versions with onlyStable option
  • Add default Slack configuration and templates
  • Add 'slack' to HookStep type for hook support Features:
  • Post release announcements to any Slack workspace
  • Rich interactive messages with buttons (View Release, Full Changelog)
  • Configurable channel (supports both names and IDs)
  • Template support for custom message formatting
  • Smart changelog condensing with full changelog links
  • Dry-run support for testing

• release: Add partial Bitbucket support (ff5cd79)

  Add Bitbucket as a supported Git provider with limited functionality. Bitbucket does not have a releases API like GitHub/GitLab, so releases are skipped for Bitbucket repositories. Changes:

  • Add 'bitbucket' to GitProvider type
  • Update detectGitProvider() to detect Bitbucket repositories
    • Checks for 'bitbucket.org' or 'bitbucket' in remote URL
  • Update getReleaseUrl() to generate Bitbucket tag URLs
    • Format: https://{domain}/{repo}/commits/tag/
  • Update providerReleaseSafetyCheck() to handle Bitbucket
    • Shows informative warning that releases are not supported
    • Allows other features (versioning, changelog, publishing, social) to work
  • Update providerRelease() to skip release creation for Bitbucket
    • Returns empty postedReleases array
    • Logs clear warning messages
    • Still triggers success hooks Bitbucket support includes: ✅ Git provider detection ✅ Tag URLs for social media posts ✅ Compare URLs in changelog (via changelogen 0.6.2+) ✅ Versioning, changelog generation ✅ NPM publishing ✅ Social media posting (Twitter/Slack) ❌ Release creation (not available in Bitbucket API) The compare URLs in changelogs are automatically handled by changelogen which supports Bitbucket format: /branches/compare/{tag2}..

• relizy: Add global tokens configuration for Twitter and Slack (caf16c4)

  Add centralized token management in the global config.tokens object, with priority system for credential resolution. Changes:

  • Create Tokens interface in types.ts with support for:
    • github: GitHub token
    • gitlab: GitLab token
    • twitter: Twitter API credentials (apiKey, apiSecret, accessToken, accessTokenSecret)
    • slack: Slack bot token
  • Update RelizyConfig to:
    • Omit 'tokens' from IChangelogConfig (avoid conflict)
    • Add tokens?: Tokens property
  • Update config.ts to populate tokens from environment variables:
    • twitter.apiKey: TWITTER_API_KEY or RELIZY_TWITTER_API_KEY
    • twitter.apiSecret: TWITTER_API_SECRET or RELIZY_TWITTER_API_SECRET
    • twitter.accessToken: TWITTER_ACCESS_TOKEN or RELIZY_TWITTER_ACCESS_TOKEN
    • twitter.accessTokenSecret: TWITTER_ACCESS_TOKEN_SECRET or RELIZY_TWITTER_ACCESS_TOKEN_SECRET
    • slack: SLACK_TOKEN or RELIZY_SLACK_TOKEN
  • Update getTwitterCredentials() to use priority system:
    1. social.twitter.credentials (specific config)
    2. config.tokens.twitter (global config)
    3. Environment variables (handled in config.ts)
  • Update getSlackToken() to use priority system:
    1. social.slack.credentials (specific config)
    2. config.tokens.slack (global config)
    3. Environment variables (handled in config.ts)
  • Update social.ts to pass both credential sources to helpers Benefits:
  • Centralized token management
  • Clear priority system (specific > global > env)
  • Consistent with GitHub/GitLab token pattern
  • Users can configure tokens once in config.tokens or per-platform in social.*
  • Better developer experience with multiple configuration options

• relizy: Add Codecov integration with optimal configuration (71f5226)

• docs: Add contributors section (b5a2a70)

• Improve error reporting for social and provider-release steps (2c17127)

  Social media and provider release failures are now non-blocking and provide detailed feedback in the final release summary. Changes:

  • Social command returns SocialResult with per-platform details
  • Provider-release returns errors in result instead of throwing
  • Release workflow displays detailed status in final log box Example output: Social media: 1 succeeded, 1 failed (slack) Provider release: Failed: Invalid token This allows releases to continue even if external services fail, while giving users full visibility into what succeeded or failed.

🩹 Fixes

• release: Add optional chaining for createdTags in success logger (886b3cd)
  • Fix TypeError when createdTags is undefined in tests
  • Use optional chaining (createdTags?.length) to safely access length
  • Change fallback text from 'No' to 'None' for clarity
  • Resolves 41 E2E test failures
  • Progress: 692/862 tests passing (80.3%)

💅 Refactors

• Restructure social media configuration (f6b8384)

  Refactor the social media posting configuration to be more modular and extensible for future platforms.

  • Removed twitter and twitterOnlyStable from ReleaseConfig
  • Added new release.social flag to enable all social media posting
  • Created new SocialConfig interface with platform-specific configs
  • Added social.twitter configuration section with:
    • enabled: Enable/disable Twitter posting
    • onlyStable: Skip prereleases (default: true)
    • messageTemplate: Custom tweet template
    • credentials: Optional Twitter API credentials (falls back to env vars)
  • More scalable architecture for adding new platforms (LinkedIn, Slack, Discord, etc.)
  • Cleaner separation of concerns
  • Platform-specific configuration
  • Credentials can be in config or environment variables Before: release: { twitter: true, twitterOnlyStable: true } After: release: { social: true }, social: { twitter: { enabled: true, onlyStable: true } }
  • Replaced --twitter flag with --social
  • Removed --no-twitter-only-stable flag (use config instead)
  • Created ResolvedTwitterCredentials type for type safety
  • Updated getTwitterCredentials to accept config credentials
  • Refactored handleTwitterPost to use new config structure
  • Updated release workflow step label to "social media"

• Create standalone social command (4c8f20a)

  Create a dedicated social command that can be used independently or as part of the release workflow.

  • Created src/commands/social.ts with:
    • social() function - Main command implementation
    • socialSafetyCheck() - Validates social media credentials
    • handleTwitterPost() - Handles Twitter posting logic
    • Full changelog generation from git commits
  • Added new command: relizy social --from x.x.x --to x.x.x
  • Changed release flag from --social to --no-social
  • Default behavior: social posting is enabled (disable with --no-social)
  • Updated release.ts to call social() command instead of inline logic
  • Integrated socialSafetyCheck() in releaseSafetyCheck()
  • Removed handleTwitterPost from release.ts (moved to social.ts)
  • Changed release.social default from false to true
  • Social posting now enabled by default in release workflow
  • Use --no-social flag to disable during release
  • Added SocialOptions interface for command options
  • Added 'social' to HookStep type for hooks support
  • Modular: Social posting can be used independently
  • Reusable: Same logic in release and standalone command
  • Testable: Easier to test social posting in isolation
  • Extensible: Easy to add new social platforms
  • Safety: Validates credentials before attempting to post Standalone: relizy social --from v1.0.0 --to v1.1.0 In release workflow: relizy release # Social posting enabled by default relizy release --no-social # Disable social posting

• release: Use bumpResult fallback when postedReleases unavailable (06909f8)

  • Add buildPostedReleasesFromBumpResult() to create releases from bump result
  • Implement priority system: postedReleases first, then bumpResult fallback
  • Handle independent, unified, and selective version modes
  • Add comprehensive logging with [social] and [social:twitter] prefixes
  • Ensure social posting works even when GitHub/GitLab releases are disabled This allows the social command to function independently of provider releases, making it more flexible and reliable in various release configurations.

• Put social dependencies in peerDependencies (6fcc1cb)

• docs: Add social features to sidebar and navbar (1e61610)

📖 Documentation

• Add social media integration documentation (9e72531)

  • Simplified README.md with social media features
  • Added comprehensive social media guides (overview, Twitter, Slack)
  • Updated provider-release docs with Bitbucket limitations
  • Fixed release config documentation (providerRelease property)
  • Updated config overview with social tokens

• Add link to CONTRIBUTING.md in README PR guidelines (fe9b08f)

• Add complete social media documentation and SEO metadata (2548a2c)

  • Create docs/src/config/social.md with detailed configuration reference
  • Create docs/src/api/social.md with API documentation and examples
  • Create docs/src/cli/social.md with CLI usage guide
  • Add SEO frontmatter metadata to slack-integration.md guide
  • Add SEO frontmatter metadata to social-media.md guide
  • Add SEO frontmatter metadata to twitter-integration.md guide
  • Document Twitter and Slack configuration options, credentials, templates
  • Include CI/CD integration examples for GitHub Actions and GitLab CI
  • Add troubleshooting sections and complete usage examples

⚠️ Breaking Changes

• release: ⚠️ Add Slack integration to social media posting (7a32114)

  BREAKING CHANGE: Add comprehensive Slack support to social command

  • Add SlackSocialConfig, SlackCredentials, SlackOptions types
  • Install @slack/web-api dependency for Slack Web API integration
  • Create src/core/slack.ts with Slack posting functionality
    • Support for rich blocks format (default) or custom templates
    • Automatic markdown to Slack mrkdwn conversion
    • Channel and token configuration with environment variable fallback
  • Create src/core/social-utils.ts for shared utilities
    • extractChangelogSummary() for changelog condensing
    • getReleaseUrl() for release URL generation
    • Shared between Twitter and Slack implementations
  • Add changelogUrl to SocialConfig for full changelog links
  • Update Twitter integration to support changelogUrl
  • Integrate Slack into social.ts with handleSlackPost()
    • Add safety checks for Slack credentials and channel
    • Support for before:slack, success:slack, error:slack hooks
    • Skip prerelease versions with onlyStable option
  • Add default Slack configuration and templates
  • Add 'slack' to HookStep type for hook support Features:
  • Post release announcements to any Slack workspace
  • Rich interactive messages with buttons (View Release, Full Changelog)
  • Configurable channel (supports both names and IDs)
  • Template support for custom message formatting
  • Smart changelog condensing with full changelog links
  • Dry-run support for testing

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.8...v0.3.0

compare changes

🚀 Features

• Add support of registry token in config.tokens.registry and config.publish.token (54b2d26)

🩹 Fixes

• Prevent git state pollution on publish failure (444006e)

  The release workflow now publishes packages BEFORE creating git commits and tags, preventing state pollution when npm publish fails. What changed:

  • Step order reorganized: Bump → Changelog → Publish → Commit → Tag → Push
  • Automatic rollback of modified files if publish fails (package.json, CHANGELOG.md)
  • Only release-related files are restored, preserving any other local changes Why this matters: Previously, if publish failed (e.g., authentication error, OTP required), the git commit and tags were already created and pushed to remote, making it impossible to retry cleanly. Now, if publish fails, your repository stays in a clean state and you can simply retry the command. The rollback is smart: it only restores files that were modified by the bump and changelog steps, leaving your other work untouched.

• Detect OTP errors from npm two-factor authentication messages (596dcfe)

  The interactive OTP prompt now works correctly when publishing to npm with two-factor authentication enabled. Previously, it would fail to detect OTP requirements and throw an error instead of asking for your code.

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.7...v0.2.8

compare changes

🩹 Fixes

• Prevent incorrect version bumps from incompatible future tags (2ca91e4)

  When bumping a stable version (e.g., 4.1.1 → 4.1.2), the system could incorrectly use tags from future major versions (e.g., v5.0.0-beta.0) as reference points, causing version calculation errors. This fix introduces intelligent tag filtering that:

  • Filters out tags with major versions higher than the current version
  • Filters out prerelease tags when bumping stable to stable
  • Preserves prerelease tags when working with prerelease versions Usage: No changes required - the filtering is automatic based on your current package version.

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.6...v0.2.7

compare changes

💅 Refactors

• Log errors in cli (63d6418)
• Rename option configName of loadRelizyConfig to configFile (a720569)

📦 Build

• Upgrade dependencies (16da2f1)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5...v0.2.6

compare changes

🩹 Fixes

• docs: Correct config examples (07248ad)
• Config type declaration - types is not required - #11 (#11)
• Exclude commits for untracked packages to avoid incorrect version updates (27e3d91)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.6-beta.1...v0.2.6-beta.2

compare changes

🩹 Fixes

• docs: Correct config examples (50d1998)
• Config type declaration - types is not required - #11 (#11)
• docs: Correct config examples (07248ad)
• Config type declaration - types is not required - #11 (#11)
• Exclude commits for untracked packages to avoid incorrect version updates (27e3d91)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.6-beta.0...v0.2.6-beta.1

compare changes

No relevant changes since last release

v0.2.5...v0.2.6-beta.0

compare changes

🩹 Fixes

• docs: Correct config examples (50d1998)
• Config type declaration - types is not required - #11 (#11)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.4...v0.2.5

compare changes

🚀 Features

• Add option to skip git tag creation during release (5fe056d)

  Allow users to disable tag creation during release using the --no-git-tag flag. Useful when you want to publish and push commits without creating git tags. Usage: relizy release --no-git-tag

• docs: Document gitTag option and improve release examples (13f9d32)

• Publish - add optional safety check to check package registry authentication (0d9c2e0)

  • Only for npm and pnpm (not yarn and bun)
  • Is disabled by default
  • To enable it, set 'config.publish.safety' to true

🩹 Fixes

• Changelog generation with wrong tags (15154ad)
• Exclude modify files from commit body (9f60547)
• Improve checking of package to bump before running release (f70e1eb)
• Do not compute new version of root package in independent mode (17a6ff2)
• Get github user profiles only if its github release (d38e61e)
• docs: Correct package.json config example (0ac9b1b)
• Publish - print new version instead the old in publish log (ead28af)
• Don't throw an error when a folder in glob patterns has not package.json, ignore the package instead (0f341aa)
• Don't throw an error when a folder in glob patterns has not package.json, ignore the package instead (271ce5f)
• Bump - don't exit with error when no relevant commits to bump (a5a58f5)
• Release - errors when release stable version from prerelease (a86a2e4)

💅 Refactors

• Use a log debug when version has changed preid" (f0e658c)
• Improve circular dependencies detection (bde3725)
• Bump - improve confirm prompt with data (c49f111)
• Improve logs while bumping package version (89f5f73)
• Improve publication logs to know exactly what is being published (aa602ba)

📖 Documentation

• docs: Improve SEO meta (06d094c)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.13...v0.2.5-beta.14

compare changes

💅 Refactors

• Improve publication logs to know exactly what is being published (56e0a9b)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.12...v0.2.5-beta.13

compare changes

🚀 Features

• Publish - add optional safety check to check package registry authentication (ff81c7a)
  • Only for npm and pnpm (not yarn and bun)
  • Is disabled by default
  • To enable it, set 'config.publish.safety' to true

💅 Refactors

• Improve logs while bumping package version (493d403)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.6...v0.2.5-beta.12

compare changes

🚀 Features

• Add option to skip git tag creation during release (9700ccf)

  Allow users to disable tag creation during release using the --no-git-tag flag. Useful when you want to publish and push commits without creating git tags. Usage: relizy release --no-git-tag

• docs: Document gitTag option and improve release examples (91ee4c3)

🩹 Fixes

• docs: Correct package.json config example (2294e31)
• Publish - print new version instead the old in publish log (3fc5c07)
• Don't throw an error when a folder in glob patterns has not package.json, ignore the package instead (757acae)
• Don't throw an error when a folder in glob patterns has not package.json, ignore the package instead (337303f)
• Bump - don't exit with error when no relevant commits to bump (f0cf9ce)
• Release - errors when release stable version from prerelease (ee87638)

💅 Refactors

• Bump - improve confirm prompt with data (d8b5788)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.6...v0.2.5-beta.10

compare changes

🚀 Features

• Add option to skip git tag creation during release (9700ccf)

  Allow users to disable tag creation during release using the --no-git-tag flag. Useful when you want to publish and push commits without creating git tags. Usage: relizy release --no-git-tag

• docs: Document gitTag option and improve release examples (91ee4c3)

🩹 Fixes

• docs: Correct package.json config example (2294e31)
• Publish - print new version instead the old in publish log (3fc5c07)
• Don't throw an error when a folder in glob patterns has not package.json, ignore the package instead (757acae)
• Don't throw an error when a folder in glob patterns has not package.json, ignore the package instead (337303f)

💅 Refactors

• Bump - improve confirm prompt with data (d8b5788)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.6...v0.2.5-beta.9

compare changes

🚀 Features

• Add option to skip git tag creation during release (9700ccf)

  Allow users to disable tag creation during release using the --no-git-tag flag. Useful when you want to publish and push commits without creating git tags. Usage: relizy release --no-git-tag

• docs: Document gitTag option and improve release examples (91ee4c3)

🩹 Fixes

• docs: Correct package.json config example (2294e31)
• Publish - print new version instead the old in publish log (3fc5c07)
• Don't throw an error when a folder in glob patterns has not package.json, ignore the package instead (757acae)

💅 Refactors

• Bump - improve confirm prompt with data (d8b5788)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.6...v0.2.5-beta.8

compare changes

🚀 Features

• Add option to skip git tag creation during release (9700ccf)

  Allow users to disable tag creation during release using the --no-git-tag flag. Useful when you want to publish and push commits without creating git tags. Usage: relizy release --no-git-tag

• docs: Document gitTag option and improve release examples (91ee4c3)

🩹 Fixes

• docs: Correct package.json config example (2294e31)
• Publish - print new version instead the old in publish log (3fc5c07)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.6...v0.2.5-beta.7

compare changes

🚀 Features

• Add option to skip git tag creation during release (9700ccf)

  Allow users to disable tag creation during release using the --no-git-tag flag. Useful when you want to publish and push commits without creating git tags. Usage: relizy release --no-git-tag

• docs: Document gitTag option and improve release examples (91ee4c3)

🩹 Fixes

• docs: Correct package.json config example (2294e31)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.5...v0.2.5-beta.6

compare changes

🩹 Fixes

• Get github user profiles only if its github release (9f7c67c)

📖 Documentation

• docs: Improve SEO meta (df629e6)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.4...v0.2.5-beta.5

compare changes

🩹 Fixes

• Do not compute new version of root package in independent mode (3be33db)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.3...v0.2.5-beta.4

compare changes

💅 Refactors

• Improve circular dependencies detection (1cd0ec7)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.2...v0.2.5-beta.3

compare changes

🩹 Fixes

• Improve checking of package to bump before running release (560dbe1)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.1...v0.2.5-beta.2

compare changes

💅 Refactors

• Use a log debug when version has changed preid" (1350fc4)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.5-beta.0...v0.2.5-beta.1

compare changes

🩹 Fixes

• Exclude modify files from commit body (e51fab7)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.4...v0.2.5-beta.0

compare changes

🩹 Fixes

• Changelog generation with wrong tags (03f3959)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.4

compare changes

💅 Refactors

• Add missing 'v' charac before version in default commit message template (57f5376)

📖 Documentation

• Update README with documentation links (458ab03)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.3

compare changes

💅 Refactors

• Use isInCI utility method to disable OTP prompt (npm) (171f957)
• Use isInCI utility method to disable OTP prompt (npm) (34f3262)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.3-alpha.0

compare changes

💅 Refactors

• Use isInCI utility method to disable OTP prompt (npm) (171f957)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.2

compare changes

🩹 Fixes

• Changelog title and compare link generation (690dcaf)

• Handle prerelease version preid changes correctly (31ab35e)

  When changing prerelease preid (e.g. alpha → beta), the function was incorrectly detecting the release type from commits and bumping the version (e.g. 1.0.0-alpha.5 → 1.1.0-beta.0 instead of 1.0.0-beta.0). Now it correctly returns 'prerelease' to keep the version in the same release line while only updating the preid identifier.

• Changelog title and compare link generation (9b8fcfc)

• Handle prerelease version preid changes correctly (1e566a9)

  When changing prerelease preid (e.g. alpha → beta), the function was incorrectly detecting the release type from commits and bumping the version (e.g. 1.0.0-alpha.5 → 1.1.0-beta.0 instead of 1.0.0-beta.0). Now it correctly returns 'prerelease' to keep the version in the same release line while only updating the preid identifier.

💅 Refactors

• Rename 'after' hook to 'success' (a0fe54c)

  The 'after' prefix was ambiguous and could be confused with timing. 'success' is more explicit and clearly indicates that the hook is executed when a step completes successfully. This aligns with the existing 'error' hook for failed steps.

• Rename 'after' hook to 'success' (b238ad5)

  The 'after' prefix was ambiguous and could be confused with timing. 'success' is more explicit and clearly indicates that the hook is executed when a step completes successfully. This aligns with the existing 'error' hook for failed steps.

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.2-beta.1

compare changes

🩹 Fixes

• Handle prerelease version preid changes correctly (31ab35e)

  When changing prerelease preid (e.g. alpha → beta), the function was incorrectly detecting the release type from commits and bumping the version (e.g. 1.0.0-alpha.5 → 1.1.0-beta.0 instead of 1.0.0-beta.0). Now it correctly returns 'prerelease' to keep the version in the same release line while only updating the preid identifier.

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.2.2-beta.0

compare changes

No relevant changes since last release

v0.2.1-alpha.0

compare changes

🩹 Fixes

• Changelog title and compare link generation (690dcaf)

💅 Refactors

• Rename 'after' hook to 'success' (a0fe54c)

  The 'after' prefix was ambiguous and could be confused with timing. 'success' is more explicit and clearly indicates that the hook is executed when a step completes successfully. This aligns with the existing 'error' hook for failed steps.

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.1.0...v0.2.0

🚀 Features

• relizy: Add lifecycle hooks system (20633be)

  Implement comprehensive lifecycle hooks system allowing users to execute custom scripts at specific stages of the release workflow. Hooks support:

  • String commands (shell scripts)
  • JavaScript/TypeScript functions
  • Three hook types: before, after, error
  • Six lifecycle steps: bump, changelog, commit-and-tag, push, publish, provider-release
  • Special hook: generate:changelog for customizing changelog generation Add CI environment detection utilities (isInCI, getCIName) to support conditional hook execution in CI/CD pipelines.

• relizy: Add lifecycle hooks system (eedda3a)

  Implement comprehensive lifecycle hooks system allowing users to execute custom scripts at specific stages of the release workflow. Hooks support:

  • String commands (shell scripts)
  • JavaScript/TypeScript functions
  • Three hook types: before, after, error
  • Six lifecycle steps: bump, changelog, commit-and-tag, push, publish, provider-release
  • Special hook: generate:changelog for customizing changelog generation Add CI environment detection utilities (isInCI, getCIName) to support conditional hook execution in CI/CD pipelines.

💅 Refactors

• relizy: Improve type definitions and documentation (ddd2d82)

  Improve TypeScript type definitions and JSDoc documentation across core modules. Export utility types (HookType, HookStep) for external use. Clarify configuration interfaces with better naming and comments.

• relizy: Improve type definitions and documentation (4a3792f)

  Improve TypeScript type definitions and JSDoc documentation across core modules. Export utility types (HookType, HookStep) for external use. Clarify configuration interfaces with better naming and comments.

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.1.0...v0.2.0-beta.0

🚀 Features

• relizy: Add lifecycle hooks system (20633be)

  Implement comprehensive lifecycle hooks system allowing users to execute custom scripts at specific stages of the release workflow. Hooks support:

  • String commands (shell scripts)
  • JavaScript/TypeScript functions
  • Three hook types: before, after, error
  • Six lifecycle steps: bump, changelog, commit-and-tag, push, publish, provider-release
  • Special hook: generate:changelog for customizing changelog generation Add CI environment detection utilities (isInCI, getCIName) to support conditional hook execution in CI/CD pipelines.

🩹 Fixes

• Exclude resources files (svg, png, etc) from commit body in generated changelog (6094991)

💅 Refactors

• relizy: Add lifecycle hooks system (5b090f6)

  Add comprehensive hook system for all release lifecycle events:

  • New hooks: before/after/error for bump, changelog, commit-and-tag, push, publish, provider-release
  • Support both function and shell command hooks
  • Hooks configurable in relizy.config.ts under hooks property
  • Automatic hook execution at each lifecycle step

• relizy: Add safety checks for provider releases (c7c37b5)

  Add safety validation before executing provider releases:

  • Check Git provider token availability before release
  • Validate provider type (github/gitlab)
  • New CLI flag: --no-safety-check to disable checks
  • Safety checks configurable via safetyCheck option in config
  • Fail fast with clear error messages when tokens missing

• relizy: Make monorepo config optional for standalone packages (6b3f7ef)

  Allow relizy to work without monorepo configuration for standalone packages:

  • Config file now optional - falls back to standalone mode
  • loadRelizyConfig renamed from loadMonorepoConfig
  • No error when config file missing (unless --config explicitly provided)
  • Display "standalone" when no versionMode defined
  • Update all imports and type references across codebase

• relizy: Improve CLI options and naming consistency (2473280)

  Improve CLI interface with better naming and new options:

  • Rename --no-release to --no-provider-release for clarity
  • Add --provider flag to manually specify git provider (github/gitlab)
  • Make --config flag optional (defaults to standalone mode)
  • Update all related config properties: release.release → release.providerRelease
  • Consistent option naming across all commands

• relizy: Add interactive OTP prompt for npm publish (cc8233a)

  Add automatic OTP handling for npm packages requiring 2FA:

  • Prompt user for OTP when npm returns OTP error
  • Store OTP in session to reuse across multiple package publishes
  • 90-second timeout on OTP input prompt
  • Detect CI environment and fail gracefully without prompting
  • Retry publish with --otp flag after receiving code
  • Support OTP priority: dynamic > session > config

• relizy: Extract OTP logic into focused functions (73eae0b)

  Improve code maintainability by breaking down publishPackage:

  • Extract isOtpError(): detect OTP-related errors
  • Extract promptOtpWithTimeout(): handle OTP input with timeout
  • Extract handleOtpError(): manage CI detection and OTP prompting
  • Extract executePublishCommand(): execute npm publish command
  • Reduce complexity of main publishPackage function

• relizy: Improve type definitions and documentation (ddd2d82)

  Improve TypeScript type definitions and JSDoc documentation across core modules. Export utility types (HookType, HookStep) for external use. Clarify configuration interfaces with better naming and comments.

📖 Documentation

• docs: Global documentation improvements (d8572dd)

• Update configuration examples and references (748140a)

  Update documentation to reflect new naming conventions:

  • Replace changelog.config.ts references with relizy.config.ts
  • Update CLAUDE.md config references

• docs: Update and improve documentation (e1eb533)

• Add CONTRIBUTING.md doc (1ec1bea)

❤️ Contributors

• LouisMazel (@LouisMazel)

v0.0.0...v0.1.0

🚀 Features

• Relizy - release manager (5c41ba1)

📖 Documentation

• Add documentation website of Relizy (ec156b0)

❤️ Contributors

• LouisMazel (@LouisMazel)