Closed amtins closed 7 months ago
I've made a test in a forked project, it seems that is working fine with no configuration, see the Release that it generated.
By default it also generates and commits a CHANGELOG in the project, the changelog can be disabled by adding the option --no-output
if desired.
I've submitted a draft based on the forked project: #172
@jboix the issue that I have is how the SemVer is handled and its consistency, a few examples:
!
is used to create a breaking change version, you can't have a body with BREAKING CHANGE
1.x.x
the breaking change doesn't seem to work wellcafebabe
which is available on HEAD
and on the latest tag
. Running npx changelogen@latest --release
shouldn't create a new version if nothing has changed. However it generates a new version with a new tag. GetGitDiff seems to behave as expected and returns an empty array when there is no diffs. In the code I see multiple issues starting from https://github.com/unjs/changelogen/blob/382eda92d13918fa5e5a354eaac04592a3fb873d/src/commands/default.ts#L44, https://github.com/unjs/changelogen/blob/382eda92d13918fa5e5a354eaac04592a3fb873d/src/git.ts#L112That said, I absolutely love this project and how easy it is to configure and I would love to use it. Maybe we could help them fixing these minor issues. What do you think?
Thank you @jboix for the PR handling the BREAKING CHANGE
https://github.com/unjs/changelogen/pull/168 👍🏽 👌🏽
We've decided to keep semantic-release as it offers more functionalities.
As a Pillarbox developer
, I'd like to know ifchangelogen
can be used instead ofsemantic-release
to potentially remove a number of development dependencies.Acceptance Criteria
changelogen
semantic-release
dependencies