I started a changelog in a8fdfef50f3337c58860edaf1ab235299a551325. I use this Markdown format in all my other packages, in the same way that Meteor does it.
The idea is not to include any documentation or minor fixes in the changelog, only changes that are bug fixes or major differences in the way the code behaves. This makes it easier for people to see what might have happened if they updated to a new version and things don't work as expected. It was always missing for this package :)
I already went through the commit history and added the relevant things for the last two versions (covering 3 months), both as an example for you and so others can see changes in the recent versions. I typically add relevant changes in as I commit or merge pull requests. Hopefully you're on board with this and can also update the history as you add things going forward. This note is just so you know that it's there.
Hi @matb33,
I started a changelog in a8fdfef50f3337c58860edaf1ab235299a551325. I use this Markdown format in all my other packages, in the same way that Meteor does it.
The idea is not to include any documentation or minor fixes in the changelog, only changes that are bug fixes or major differences in the way the code behaves. This makes it easier for people to see what might have happened if they updated to a new version and things don't work as expected. It was always missing for this package :)
I already went through the commit history and added the relevant things for the last two versions (covering 3 months), both as an example for you and so others can see changes in the recent versions. I typically add relevant changes in as I commit or merge pull requests. Hopefully you're on board with this and can also update the history as you add things going forward. This note is just so you know that it's there.
Cheers, Andrew