It’s hard to keep track of all the changes and I think it would be nice to have a changelog included in the component docs.
Have you read the release notes?
I can breeze through them for breaking changes and any components I use in a few minutes.
I’m not saying it’s a bad idea, but this would generate quite some overhead for the developers. If something has changed users need to be aware of, that’s usually part of the breaking changes. So for me personally it would be enough to have a way of quickly looking up the breaking changes. As if those blocks of the release-notes had some special tag, and then I’d query for all breaking changes dating back to whatever release I set the limit and only get those blocks displayed without having to read through the whole release-post.
But would it really? The breaking changes are already labeled in github, as is the component. So having component-specific changelogs could be based on that – another question is of course that this requires more thought on writing changelog entries that are understandable for users, too.
As a rule of thumb: developers hate documentation. The least possible amount of work spent on documentation is the best amount. 