-
Notifications
You must be signed in to change notification settings - Fork 231
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
Add a change log #68
Comments
Great idea. Thank you for explaining so well. |
It would help to work on feature branches instead always over the |
@fridays If you agree I can contribute with the changelog. IMO we could use the conventional commits and automatically generate a changelog.md file with the standard-version package. Benefits:
|
Just pushed this PR #78 Is really easy to use and project would benefit from having tag releases and changelogs. |
Thank you, that looks very useful. semantic-release and zeit/release sound good too. Anyone experience with the pros and cons? |
I just made a github release using |
It would be awesome if a
changelog.md
was added and Github releases were used to keep track of changes.A common practice is to track changes under a
next
version heading at the top ofchangelog.md
, then when ready to release:package.json
.next
heading inchangelog.md
to the new version.npm publish
.You can see that process in action at jaydenseric/apollo-upload-client.
The text was updated successfully, but these errors were encountered: