feat: inferring the semver version according to Conventional Commit #71
Conversation
This file contains 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
Yeah, I agree that. Are you interested in maintaining one you own so we can depends on it? |
antfu
reviewed
Jan 23, 2025
Yeah, of course. I will do this and update in this PR, so this PR I will turn into draft for now. |
|
The code has been updated to use the In addition, set the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
parseCommitscodetargettoesnextsince regular expression capture named groups are only used ines2018and aboveLinked Issues
closes: #69
Additional context
1. Publishing parseCommit as a separate package?
Now that bumpp, unjs/changelogen, and changelogithub all handle git log messages, I was wondering if it would be possible to release this part of parseCommit as a separate npm package?
Even though the conventional-commits-parser package already exists, it's too big, contains a cli program, has an unacceptable install size of 400kb, and its maintenance seems to be inactive.
Or maybe bumpp could just depend on unjs/changelogen and use its exported parseCommits, like changelogithub does?
2. Default release type
Now, I still have
nextas the default option for promptNewVersion, do we need to change it tosemveror somehow make it default tosemver(I thought someone might like that)?最后，小年快乐！