[Request]: Add a changelog

[AngryEndUser]

Problem

It's currently difficult to track what has changed between versions. There is no changelog, and many commits have minimal or unclear descriptions (e.g. 93ec427f64588eebec32d07f6b9b71634b11f6f4 or 2cad4fbd5c231a9b371bdae1d3a56827254c0972). This makes it hard for users to understand the impact of updates without digging through the code. It's especially frustrating when a change could silently render the previous %appdata%/YimMenuV2 folder obsolete, forcing the user to delete it and reconfigure their settings. Understanding C++ helps, but shouldn't be required.

Solution

Please consider adding a changelog (e.g., CHANGELOG.md) that summarizes what’s changed in each version. This doesn’t mean you need to adopt semantic versioning as discussed in #378, just that changes are documented somewhere.

Even simply improving commit messages to clearly state what has been fixed/improved/added, and whether %appdata%/YimMenuV2 needs to be deleted would already be a big step forward. For reference, Keep a Changelog offers a great format you might consider adopting.

Reason

N/A

Additional context

N/A

[maybegreat48]

It's especially frustrating when a change could silently render the previous %appdata%/YimMenuV2 folder obsolete, forcing the user to delete it and reconfigure their settings

That should never happen. If it does, please report it ASAP

[alzhetv]

You can simply use this URL https://github.com/YimMenu/YimMenuV2/commits/enhanced/ to see the complete changelogs. Seriously, this is the best changelog you can always check at any moment. And if you see the little ✔️, you can even download development builds ! Doing a Changelog.md is extra-work and not really needed because of the commits page already serves this function.

[xesdoog]

I don't think a markdown file is a good idea because you'd wanna see the changelog history and we can't write everything to the file because it will grow larger over time and become unreadable and we can't overwrite the file with every new release either because that defeats the purpose of "changelog history". We could however edit the release workflow to write the last commit message and body to the release page. This would of course require contributors to submit clear and concise commit messages because that's where the workflow will grab the changelog text from and if that's strongly enforced then we don't need to change or add anything and you could simply navigate to the commit history URL.