-
-
Notifications
You must be signed in to change notification settings - Fork 304
fix(1694): changelog_merge_prerelease not working on cz bump #1700
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v4-11-0
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| ## 0.2.0 (2025-01-01) | ||
|
|
||
| ### Feat | ||
|
|
||
| - add new output | ||
|
|
||
| ### Fix | ||
|
|
||
| - output glitch | ||
|
|
||
| ## 0.1.0 (1970-01-01) | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Quick question, is this expected?
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I assume you mean the empty version I would say yes. Reason is that an annotated tag is created on a version that has no eligible commits e.g.
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for detailed explanation. I don't think it's a blocker. @woile wdyt
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, this is how it works. The version tagged has no elegible commits, so the changelog creates an empty entry. I don't expect this to change, users can go and fix it themselves, as commitizen does incremental updates to the changelog. This scenario would probably happen in a project which is not using conventional commits (or other set of rules), and it starts using it. Or if a mistake is made, but maintainers of a project can still update the changelog manually |
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| ## 0.2.0 (2025-01-01) | ||
|
|
||
| ### Feat | ||
|
|
||
| - add new output | ||
|
|
||
| ### Fix | ||
|
|
||
| - output glitch | ||
|
|
||
| ## 0.1.0 (1970-01-01) |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| ## 0.2.0 (2025-01-01) | ||
|
|
||
| ### Feat | ||
|
|
||
| - add new output | ||
| - more relevant commit | ||
|
|
||
| ### Fix | ||
|
|
||
| - output glitch |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| ## 0.2.0 (2025-01-01) | ||
|
|
||
| ### Feat | ||
|
|
||
| - add new output | ||
| - more relevant commit | ||
|
|
||
| ### Fix | ||
|
|
||
| - output glitch |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| ## 0.2.0 (2025-01-01) | ||
|
|
||
| ### Feat | ||
|
|
||
| - add new output | ||
| - more relevant commit | ||
|
|
||
| ### Fix | ||
|
|
||
| - output glitch |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| ## 0.2.0 (2025-01-01) | ||
|
|
||
| ### Feat | ||
|
|
||
| - add new output | ||
|
|
||
| ### Fix | ||
|
|
||
| - output glitch | ||
|
|
||
| ## 0.1.0 (1970-01-01) |
Uh oh!
There was an error while loading. Please reload this page.