Better document the changes users might see.

[ltratt]

I (re)migrated a project using grmtools-0.12 to see what breaks and realised that we'd missed some things out in CHANGES.md. This commit adds in all the things that I know users will encounter (there might be others, but hopefully not!).

@ratmice I'm starting to think that we're also getting to the right point to make a 0.13 release. Are there any other parts of the API that you can see should be considered for change before we do so?

[ratmice]

All good catches, in updating my own projects and various random downstream projects, I've only run into 2 of these 3 cases listed as major changes. (The escaping one which is there already and the unused token/rule case here). Sorry I have been a little lackadaisical about keeping the CHANGES.md file up to date as we land these changes.

bors r+

[bors]

Build succeeded:

• buildbot/buildbot-build-script

[ratmice]

@ratmice I'm starting to think that we're also getting to the right point to make a 0.13 release. Are there any other parts of the API that you can see should be considered for change before we do so?

Forgot to respond to this. There isn't anything critical, I had looked at #349 and it is going to take some thinking since it delays the time at which we may first have a YaccGrammarKind until much later than we currently do, and there are various assumptions that we have one. That being such a larger change relative to the minor enhancement it provides I don't think it may not be worth delaying, or trying to rush getting that in the release.

[ltratt]

Hmm, yes, #349 might not be worth waiting for. OK, my plan is to make a 0.13 release tomorrow PM GMT/UTC, unless anyone thinks of something that should cause us to pause.