Skip to content

v1.4.8

Latest
Latest

Choose a tag to compare

View all tags
@LouisMazel LouisMazel released this 10 Jun 14:57
v1.4.8
0e7a6af

compare changes

🩹 Fixes

  • relizy: Commit types with a title now appear in changelogs and release notes (cb3dc6a)

    Types configured with only a title (e.g. docs: { title: '📖 Documentation' }) now display in CHANGELOG, GitHub/GitLab releases, and social media posts. These types still don't trigger version bumps — only types with a semver field do. Use false to exclude a type entirely.

  • Detect and recover from orphaned release tags after rebasing (b4d6478)

    When a branch is rebased after release, its tag can point to a commit no longer in history, causing incorrect changelog spans and unnecessary package bumps. Relizy now detects this and uses the correct commit range. In non-interactive environments, it auto-corrects with a warning; in a terminal, it prompts you. The tag name is preserved and no commits are rewritten.

    New config options:

    detectRewrittenTags: true,           // Enabled by default
onRewrittenTag: 'ephemeral',         // 'prompt' | 'ephemeral' | 'rebind' | 'error'

  • Redact secrets in debug logs (d2d9ed9)

    Tokens (npm, GitHub, etc.) are now masked in debug output, so sharing logs doesn't risk exposing credentials.

  • Stop hanging on registry authentication checks (52cc132)

    Registry authentication checks that never received a response now timeout after a short delay and show a clear error instead of hanging indefinitely. Customize the timeout with publish.safetyCheckTimeout (default 15s) or disable the check with --no-safety-check.

  • Respect custom registries from .npmrc (345f09b)

    Relizy now honors a custom npm registry configured in .npmrc (like a corporate proxy) instead of always forcing the public registry. If your .npmrc points to a private or proxied registry, that's what Relizy will use. Set publish.registry only when you need to override it explicitly.

  • Show first and last characters of masked secrets in logs (216f5f8)

    Masked tokens in logs now retain a few characters at the start and end (e.g. npm_***2Hwk) for identification, instead of full redaction. Secrets shorter than 16 characters remain fully masked.

📦 Build

  • Upgrade maz-ui dependencies (d827532)

❤️ Contributors

Assets 2
Loading