fix #191: generate changelog from pull requests using lerna-changelog #253
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
Closed
silkentrance
force-pushed
the
gh-191
branch
2 times, most recently
from
fc60088
to
113651e
Compare
|
lol this must be microsoft at work. buggy as hell. it took three tries to actually merge this. |
This was referenced Mar 14, 2021
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.
fix #191: generate changelog from pull requests using lerna-changelog
@raszi
Prior to publishing a new release, the changelog must be updated.
To do this, simply run
./scripts/prepare-changelog.sh <previous-version-tag>.This will create a CHANGELOG.new.md based on the old CHANGELOG.md.
Normally, this will give you an unreleased new version at the very top.
Here you must insert the actual version number.
After review, simply move the CHANGELOG.new.md to CHANGELOG.md and you are done.
Have fun.