I’d just come to the post on the community page.
Scroll up to the top of this page and look at breaking changes
Err… Ok. The community post is just some copy w/o formatting…
The blog post is the master. The OP here is not even updated with the point releases, afaict
Suggest you log an issue here, although there seems to be one regarding 7.1 to 7.2 and zha futher down, but it seems your already on that. Issues · home-assistant/operating-system (github.com)
Yes, I’m seeing that now. Might be an idea to link folk to the actual post in the first part of the post.
Now I knew it might be there and looked for it, I found this.
Rather than putting this as an afterthought (really small text), perhaps put it at the top as the first line under the image?
This reminds me of another annoyance, finding the old release notes - there is no Blog Index
Even if you click on the Blog Category, the listing doesn’t have the release number…
[edit]
BTW, it is easy to find things when you know where they are. This is a comment from someone who didn’t know where it was and trying to suggest improvements for those following on
Thanks, but again, you need to know it is there to find it.
Thanks for that link @ledeeus. bookmarked
Not really, all blog posts have categories under the header, click it and you are there.
I love RSS, it is absolutely brilliant
Core not listed as a category in the index.
Yes, it is under the post…
[edit]
@ludeeus why do the headings change depending on which category you click? If I select the Announcements category, the Blog post title is different to the Core category listing?
Thanks, but could I ask the link to the main Blog post is included at the top of the community post and not the bottom, please?
TBH, I’d only include the link. The post here is indeed unreadable, so the less confusion, the better
That is a good shout especially as the post is not updated with subsequent releases.
Thanks for sharing. I wish that were mentioned on the top post as I was clicking “Check for updates” every few hours thinking that it was an issue on my end.
2022.2.5 should be incoming shortly with the fix in it