Changelog format change request

[JollyRgrs]

Describe the improvement

I understand how the changelog's changes are posted, but is there any way possible to standardize this so that the thing that is being changed (the integration, or whatever else). I like to skim the changelog for things that pertain to me. There are many that don't at all but also many that do. When looking at a large list of changes it is hard to simply skim it when I have to read every line to find the affected "things". The format and location of the things is not consistent and therefore really hard to read without reading the entire thing.

Is there any way at all to standardize the change comments to have the affected item first?

Just a starting point (please feel free to pick it apart). I know things aren't always so cut and dry, but the more that could be in this format it would make it much easier to look at to see if it affects me or not and what to watch out for knowing that something changed on the backend.

aioesphomeapi: Bump to 44.24.1
Matter: Fix fractional setpoints in matter climate not rounded
influxdb: Fix to reconfigure for v1 configuration

Anything else?

No response

[BlackRockCity]

I also felt like a fix was needed, then I found your post. I designed this prototype changelog format to improve the existing paradigm. Your thoughts are welcome.

Free under the Apache 2.0 license.

Readme

Live Prototype

HA Forum Announcement of the new prototype.

[JollyRgrs]

Nice work, @BlackRockCity

I really like the tables/sorting. The only suggestion I would throw in is to put the integration/area in the first column. If I'm skimming through for what matters to me, that makes it easiest to skip over things I don't worry about without losing my place. I also love the category and being able to sort the simple dependency fixes to the bottom (good things to know about, but generally a non-issue, nothing to worry about).

Question:

How would this integrate into the current format? Right now it is an initial YYYY.MM.0 post about all the big things going on and then the .1, .2, and so on are put at the bottom. I don't want to lose the .0 format because I do like that, but would like this to be below it maybe? I think I'd rather it be all on one page then have to switch between pages but I'm terrible at designing UX, I just give good feedback. I'm unable to come up with a solution.

[BlackRockCity]

I have made a few python apps to pull down github, jira, bugzilla, gitlab, Launchpad, Redmine, etc PR changes via their APIs. Then AI summarizes the changes to create the quick summary at the top and to assign areas to each PR. Another app generates the static files like the html page you saw. Its a work in progress but showing promise. It turns out to be a fairly sophisticated problem to do this across thousands of different types of software projects and dozens of bug trackers.

I haven't looked into this carefully, but I don't get any PR data when I draw down release 2026.5.0. Without data, I cant generate a change log for that release. However, all other dot releases do have PR data.

The webpage has improved slightly since the preview I posted. Having area as column 1 is possible but slightly problematic because its not complete or consistently present in all software projects. It might work for HA.