-
-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
automate releases #309
automate releases #309
Conversation
release-it has already dropped node 8 support. Will rebase after #308 is merged. |
Cool tooling. Looks good to me 👀 I have gone through the PRs since the last version and tried to label them. Probably worth double-checking the labels I have used are correct. |
0b5fae7
to
3c2e6a3
Compare
Rebased after #308 has been merged. Tests should pass now. |
You motivated me to do the same for the other PRs and update the changelog which was very outdated. This also includes a nice example of how the generated changelog looks like into this pull request. |
I think this branch needs a rebase. Love the new changelog ❤️ |
8b23ed5
to
d2a243e
Compare
Rebased. |
This setups
release-it
andlerna-changelog
to automate the release process. It also documents the required process inRELEASE.md
.Before doing the release the pull requests must be labeled correctly to be picked up by lerna-changelog.
This is based on
rwjblue/create-rwjblue-release-it-setup
. The first commit uses the current defaults. Second commits applies the changes proposed in rwjblue/create-rwjblue-release-it-setup#15.It's splitted in two commits to ease review. Please squash on merging.