Semantic release support

[gargroh]

These changes will help in automating the whole package release workflow including :-

• Determining the next version number
• Generating the release notes
• Publishing the package

No need to maintain changelog now, details will be visible via Releases tab in github with other meta data.

@tannerlinsley to enable releases please add npm publish and github token in secrets

[tannerlinsley]

So what happens if I merge or create commits that don't have any of these template prefixes? What happens? I mostly just want this to be forgiving.

[gargroh]

Yeah, if commits does not follow template, then it will ignore them and no release.

So how it goes - It analyses all commits one by one made since last release and chooses the highest version. For ex - 5 commits are there since last release then in ci logs it will show something like -

Analysing 1 'commit msg' - no relese required
Analysing 2 'commit msg 2' - patch release required
Analysing 3 'commit msg 3' - minor required
Analysing 4 'commit msg 4' - no release required
Analysing 5 'does not follow template' - no release required

Then it will conclude to make minor release.

[tannerlinsley]

Awesome. I'll admit, I am weary to hand over release control to this, but am willing to give it a shot.

[gargroh]

Thanks, sounds good.

[gargroh]

@all-contributors please add @gargroh for tool

[allcontributors]

@gargroh

I've put up a pull request to add @gargroh! 🎉