Improve changelog

[st-pasha]

I suggest that the changelog can be improved if each entry included a reference to a relevant issue/PR.

For example, instead of

 - `changePriority` no longer breaks game loop iteration
 - Move component mixin checks to their own files
 - Fix exception when game was rebuilt
 - Add `@mustCallSuper` on `Component.render`

we would say

 - `changePriority` no longer breaks game loop iteration (#998)
 - Move component mixin checks to their own files (#992)
 - Fix exception when game was rebuilt (#1003)
 - Add `@mustCallSuper` on `Component.render` (#1011)

When viewing the Changelog, Github will render these as links, so that if anyone wants to learn about each particular change in more details, they could simply follow the link.

[OlegNovosad]

Agree on that! Does it make sense to also include contributors? In such case it can give more boost in motivation maybe. Usually other products do this.

[spydon]

We are moving to Melos once v1 is released, in Melos the changelog is generated from the PRs instead of a file that you manually edit.

[Salakar]

https://pub.dev/packages/melos/versions/1.0.0

[Salakar]

Hey folks, lmk if you want a hand with your first melos powered release since I'm still working on docs for adopting melos versioning/releases for existing repos, but the main TLDR is;

For your very first use of melos version use the --since flag and the commit sha of your last commit relating to the previous release (e.g. b6ddae5) and melos will start from there.

You may need to keep using the since flag until all your packages have had a release through melos as your current git tags are not compatible, melos uses the format used by flutter and official plugins <packageName>-v<version> (yours does not have the 'v' it seems, maybe melos should allow other formats here also 🤔). Alternatively if you create new tags in that format for all your existing versions on that commit sha I linked earlier then melos should be able to go from there without needing to use since flag.

Please let me know if there's anything you need or that is blocking you.

Also check out the FlutterFire release process docs since they cover releases using melos including how to review changelogs manually should you need to (similar docs will be added to official melos docs).

[st-pasha]

Is there a way to automatically filter out certain PRs from the changelog? For example, if we don't want to include anything tagged as chore:, build: or refactor:?

[spydon]

Is there a way to automatically filter out certain PRs from the changelog? For example, if we don't want to include anything tagged as chore:, build: or refactor:?

I think we should include everything, the changelog is for us too. :)

[spydon]

Hey folks, lmk if you want a hand with your first melos powered release since I'm still working on docs for adopting melos versioning/releases for existing repos, but the main TLDR is;

For your very first use of melos version use the --since flag and the commit sha of your last commit relating to the previous release (e.g. b6ddae5) and melos will start from there.

Sounds easy enough!

You may need to keep using the since flag until all your packages have had a release through melos as your current git tags are not compatible, melos uses the format used by flutter and official plugins <packageName>-v<version> (yours does not have the 'v' it seems, maybe melos should allow other formats here also 🤔). Alternatively if you create new tags in that format for all your existing versions on that commit sha I linked earlier then melos should be able to go from there without needing to use since flag.

I think we'd be fine with a new tag format, not sure why we don't have a v.

Please let me know if there's anything you need or that is blocking you.

Can we choose the version number ourselves? We are going to be more flutter style in versioning than semver.

Thanks for being so supportive! 😊