Keep a changelog

[viblo-majority]

Is your feature request related to a problem? Please describe.
Its very difficult to know what is changed between releases since I have to read the commits. That makes it both difficult to know if issues are fixed by upgrading, or to know if its safe to upgrade to a new version or not, e.g. will it break things.

Describe the solution you'd like
Keep a changelog. Exactly how is not that important, but Ive seen many dotnet libraries uses the release feature in Github, like here https://github.com/riok/mapperly/releases/tag/v4.3.1 for example.

Describe alternatives you've considered
None.

Additional context
n/a

[BifrostTitan]

A lot of it is automated github actions that generate the changelogs. We simply don't have it setup on this repo. I tossed the commit history through github copilot and had it generate a changelog. I will keep it updated for future releases. We dont release raw dlls through github because they are not signed by the publisher. Using strictly nuget for supply-chain security features like Microsoft’s package signing infrastructure, GitHub’s Dependabot alerts, and CVE vulnerability scanning.

ebec9e1