search

zachdaniel / git_ops

A tool for version and changelog management in Elixir via conventional commits.
MIT License
134 stars 24 forks source link

A braking change can be specified with ! appended after, not before, the type/scope #20

Closed djantea closed 4 years ago

djantea commented 4 years ago

As per v1.0 of the Conventional Commits spec, a breaking change commit can be specified either by a BREAKING CHANGE: footer or a ! after the required type and the optional scope.

The given exemple is:

refactor!: drop support for Node 6

So we need to accept the above, as opposed to

!refactor: drop support for Node 6
zachdaniel commented 4 years ago

Oof, great catch!

zachdaniel commented 4 years ago

19 was merged and released as version 0.6.4 on hex.

zachdaniel commented 4 years ago

Sorry, wrong issue :)

zachdaniel commented 4 years ago

Released on hex as version 1.0.0 (breaking change incurred major release bump, and this has been around it might as well be 1.0 :)