Skip to content

Add semanting release bot #81

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

Closed
afontcu opened this issue Aug 11, 2019 · 2 comments
Closed

Add semanting release bot #81

afontcu opened this issue Aug 11, 2019 · 2 comments
Labels
chore Changes to things that do not actually go into production has PR There's an open PR to solve/close the issue

Comments

@afontcu
Copy link
Member

afontcu commented Aug 11, 2019

Other Testing Library members are using https://github.com/semantic-release/semantic-release to handle their releases.

It looks great not only because of the sensible version bumping, but also for all the automated tasks it handles (notifications, formalized commits,...).

Thoughts?

@dfcook
Copy link
Collaborator

dfcook commented Aug 13, 2019

Would be very happy to go with this, getting the release process into CI was one of the things on my todo list.

@afontcu
Copy link
Member Author

afontcu commented Aug 13, 2019

Great! semantic-release relies on commit messages to infer new versions, so AFAIK that would mean implementing a tool such as commitizen.

Not sure what are the implementation steps, but I'll open a PR so that we can see what are the main changes.

@afontcu afontcu added the chore Changes to things that do not actually go into production label Aug 14, 2019
@afontcu afontcu added the has PR There's an open PR to solve/close the issue label Aug 15, 2019
@afontcu afontcu closed this as completed Aug 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Changes to things that do not actually go into production has PR There's an open PR to solve/close the issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants