Release notes are always absent of build system changes

[worldofpeace]

Describe the bug

I've noticed with how release notes are now being handled they basically never contain information that pertains to changes in the buildsystems/dependencies.

I prime offender would be https://github.com/elementary/wallpapers/releases/tag/5.5.0, which Meson build system support was added and there's no mention of this. This is particularly frusterating for me as a distro maintainer, changes in the build system or dependencies are often the most important information.

I do understand this is performed in a more automated way, so it would be nice if this information could be included again. Otherwise I actually have to manually read the git log for this information on the relevant files.

Thanks. worldofpeace ✨

[worldofpeace]

An easy requirement you could do here is make all build system related changes have their commit message prefixed with build, and if there's multiple build systems $buildsystem. And just pull in those.

[cassidyjames]

@worldofpeace we use a sanitized commit log for the debian changelog, we could also list that on the release instead of just AppData info. i.e. on the release have something like this:

User-facing changes:

• Change default wallpaper to Sunset by the Pier

Relevant commits:

• Release 5.5.0 (gettext-flatpak: Add a parameter to specify push branch #87)
• Add Release to Actions
• Run test script with GitHub Actions (Gettext: update polkit package name #86)
• Add AppData (release: Update to Debian Trixie #85)
• Update main.yml
• Add Build CI to Actions
• Add symlink back to master
• Split deb packaging into its own branch
• Use Meson build system (README: Fix broken links and update checkout version in the examples #84)
• Delete CODE_OF_CONDUCT.md
• Refix white pixel in Ashim DSilva (gettext-flatpak: Remove unwanted "steps:" #83)
• Redo 5.1 symlink (Dockerfile: use dev target #81)