I put together a small tool for the 2026.9 release called Release Lens.
Home Assistant release notes can get pretty long, so the idea is simple: select or paste the integrations you use and it filters the release notes down to the changes that may actually be relevant to your setup.
It’s completely browser-based—no Home Assistant login, URL, token, configuration upload, or installation. Every result links back to the corresponding official Home Assistant source.
It’s meant to be a quicker way to scan a release, not a replacement for the official notes.
I’m curious whether this is actually useful to other people. If you notice something classified or mapped incorrectly, let me know.
Thanks both, glad it’s useful. I added the paste-a-list option so people with a lot of integrations wouldn’t have to select them one at a time. The main goal was just to make it quicker to get from the full notes to the handful of changes relevant to a particular setup.
Yes there are often 2-3 urls to Frontend Updates i.e ( Update frontend to 20260826 … )
And these url’s is just “another” placeholder where you can find a link to the frontends changelog(s).
( And in this new HA "2026.9 release >>> full announcement , There Are atleast 3 of these "Frontends Extremely Cumbersome Way of getting updated about the Frontend Changes )
These Changes are in fact very important( and often breaking changes ), and for some weird reason These (small and large) Changes does not have a “prominent” Placeholder/Direct-Liink in the Official Release Blogs
Ok my rant , But i still can’t understand Why TH, they still don’t Highlights the Frontend Change Log (All, as there is often xxxxxx.0 /.1 /.2 /.3 ) Included in The CORE Releases.
Anyway , my question was, will this your “Release Lens” traverse the Release Blog, and follow all links, or will it be possible to type in the url of any of these “Github release logs” and Filter there ?
Yes, it’s built for the 2026.9 release right now, but I plan to update it for future Home Assistant releases. For this version I used the main release notes, the full Core changelog, linked PRs, and relevant developer notes, so it already goes beyond the release blog itself.
It doesn’t currently accept arbitrary GitHub URLs or automatically crawl every linked changelog. Your point about frontend releases, including the .0, .1, and .2 updates, is a good one. I’ll make that frontend release chain an explicit source check in future updates so those changes don’t get missed. Thanks for pointing it out.
Ok, yes i honestly find it “useful” as it’s the 2 url’s i posted above which are relevant( And Cumbersome to go through ) , not the Blog-Post, Or Release Note ( As those are just a “presentation” for the “public” ) And Often just a fraction of what is actually done /“Released”
( I usually search the Full Change Log, for i.e frontend, and the various integrations i find reasons for , but now have a permanent link to i.e frontend, as i always go through that anyhow )
While speaking(writing) frontend is now 20260826.6 !!! ( And how many people do you think are aware , or know what happened “suddenly” to their HA )
Im still amazed that this " goes under the radar ! "
Yeah, that makes sense. The frontend updates are probably where this could be most useful, especially when they’re already up to .6. I’ll make sure I check the whole frontend release chain for future versions. Thanks again.
I would rather like if it looked like real release notes, not AI Slop (I am not saying AI is bad, just without design guidelines, 92percent of AI projects look the same dark gradient look with many things that are not useful but lacking useful things), but filtered.
But anyway, this is not very useful to me; I like to read everything…
Fair points. This first version is only for 2026.9, but the plan is to update it for future releases if people find it useful. I also hear you on the design. A simpler look closer to the official notes would probably fit the tool better. And if you prefer reading everything, the filter may just not fit your needs.
, not the Blog-Post, Or Release Note ( As those are just a “presentation” for the “public” ) And Often just a fraction of what is actually done /“Released”