Include a changelog for the specification itself

[eemeli]

I guess this counts as a bit of a request for dogfooding?

I am using conventional-commits and tools based on it. Currently, when I notice that the website's version has updated itself, I need to look through the commits on GitHub to find out what happened. This is clumsy. What I expected to find was a changelog available somewhere that would summarise the changes for me; this is effectively the most significant reason why I'm encouraging developers around me to use the spec in the first place.

Or did I just not find the changelog, and this is really a request for linking to it more clearly?

[bcoe]

@eemeli great point :+1: the cobblers children have no shoes?

Would happily accept a PR adding a CHANGELOG, standard-verison is what I use on all my libraries ... and it's about to have a PR lands that makes it compliant with the latest and greatest rules we're describing in this specification.

[damianopetrungaro]

@eemeli do you want to work on it?

[eemeli]

@damianopetrungaro I'm afraid I don't really have the bandwidth available for this atm.

[bcoe]

@damianopetrungaro I'd be happy to take this on, I think we need to come up with some guidelines for how we tag the different variety of commits to this repo however; as working on a spec document is a bit different than a module ... almost every change could be argued to be docs.