Automated changelog creation #601
Merged
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
…trigger it in stable deployments
…o the last commit of the current branch to avoid problems with not existing tags (created later). Added some script documentation. Also changed script param name `next` to `release-name` to better reflect what it's used for.
…rt its work starting with 6.4.0 already.
Pull Request Test Coverage Report for Build 2317
💛 - Coveralls |
devbucket
approved these changes
Apr 4, 2019
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
Starting from now, the changelogs will now be created upon version builds using
lerna-changelog.Type of change
Please add an "x" into the option that is relevant:
How to test it
Check the changelog after creating a release. Make sure, that it is not duplicating any entries, when the "latest" version title is already placed in the file.