chore(release): next#102
Merged
Merged
Conversation
… outputs
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.
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
```ts
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 (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.
A release could freeze indefinitely, with no message, while checking 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`.
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.
Deploying relizy with
|
| Latest commit: |
1a7d8f1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://d57d2ecf.relizy.pages.dev |
| Branch Preview URL: | https://develop.relizy.pages.dev |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #102 +/- ##
==========================================
+ Coverage 81.44% 81.71% +0.26%
==========================================
Files 29 30 +1
Lines 2916 2958 +42
Branches 872 883 +11
==========================================
+ Hits 2375 2417 +42
Misses 308 308
Partials 233 233
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Owner
Author
🚀 Release published
Packages
Installationpnpm add relizy@1.4.8-beta.0or using the pnpm add relizy@beta |
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.
Owner
Author
🚀 Release published
Packages
Installationpnpm add relizy@1.4.8-beta.1or using the pnpm add relizy@beta |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.