v1.4.8-beta.0

compare changes

🩹 Fixes

• relizy: Commit types with a title configuration now appear in changelogs and release notes without triggering version bumps (cb3dc6a)

• Automatically detect and recover from release tags orphaned by branch rebases, preventing duplicate commits in changelogs and unintended package bumps (b4d6478)

  Relizy now detects when a release tag points to a commit no longer in the history (after a rebase) and uses the correct commit range. In non-interactive environments, this auto-corrects with a warning; in a terminal, you are prompted. No commits are rewritten and nothing is mutated in dry-run mode.

  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',
  })

• Tokens and API credentials are now redacted in logs (d2d9ed9)

• Registry authentication checks now timeout instead of hanging when the registry is unresponsive (52cc132)

  You can adjust the timeout delay with publish.safetyCheckTimeout (15s by default) or skip the check with --no-safety-check.

• Custom npm registries configured in .npmrc are now respected during publishing and authentication checks (345f09b)

  When publish.registry is not configured, Relizy resolves the registry from your npm settings, so proxies and private registries work without additional setup. Set publish.registry only to force a specific registry.

❤️ Contributors

• LouisMazel (@LouisMazel)