-
Notifications
You must be signed in to change notification settings - Fork 32
Release v0.3.0 (Minor) #274
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
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
bhufmann
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A lot of features went in since 0.2.0 release. So, I think this should be a minor release to 0.3.0 instead of 0.2.1.
af5602d to
5fa844e
Compare
|
The following 1 GitHub releases will be created once this pull request got merged. Release v0.3.0 with changes since v0.0.0
|
Updated. I kept the branch name the same, but that should only visible in the PR. |
|
Afterwards I can manually create a GitHub release for the couple of earlier versions (v0.1.0, v0.2.0), and move there the relevant part of the automatically generated release notes. |
bhufmann
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. Go release! Thanks
|
Thanks for the review! |
Trigger a release (v0.3.0) to confirm our automated release/publish infrastructure is working as intended. This was done following these instructions (README.md)
Upon merging this PR, we expect:
v0.3.0GitHub release is created, with associated release notes (auto-generated)v0.3.0git tag is created[email protected]package is published to npm