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
Took a swing at upgrading
conventional-config
andconventional-recommended-bump
.conventional-config
was a pretty easy upgrade - almost nothing has changed there.It was a bit more tricky with
conventional-recommended-bump
as they've changed API completely. In every case there is a (undocumented) migration path though. In this PR I took the direction of rewriting the "old API" to new one within the library so the migration for@release-it/conventional-changelog
users would be as easy as possible.But honestly? Looking at this now, I think there should be a breaking change introduced in
@release-it/conventional-changelog
to redo the options passed to the plugin. New API could look like this:After doing this change it would be pretty easy to write a simple migration docs and say which old options go where in the new API - it's clearly visible in this PR.
By doing this
@release-it/conventional-commits
will remain as transparent as possible - it'll still just pass options to underlying APIs.But, in the end it's your decision @webpro, so feel free to continue with this migration as you think is best.
Cheers ✌️
Resolves
#88