-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix: use conventionalcommits in semantic-release #3
Conversation
6b980f8
to
073cf8f
Compare
module.exports = [ | ||
{ | ||
type: 'improvement', | ||
release: 'patch', | ||
}, | ||
]; |
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.
The conventionalcommits
spec has two commit types in addition to the ones in the angular
preset: chore
and improvement
. The chore
type shouldn't trigger a release.
There are other commit types that aren't included in the default release rules, but none of those should trigger a release either.
d52c42e
to
bfb6e48
Compare
Fix an assumption around how semantic-release would interpret commit types by using the conventionalcommits preset.
bfb6e48
to
6d86eb0
Compare
An improvement that's anything more than a bugfix cannot merely be a patch release, per the semver spec.
6d86eb0
to
63fb94b
Compare
Forgive the force-pushes - I was having some personal problems. |
🎉 This PR is included in version 1.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Fix an assumption around how
semantic-release
would interpret commit types by using theconventionalcommits
preset.Upstreamed
improvement
type release rule support: semantic-release/commit-analyzer#149.