Small changes to the 2025.6 release notes #39407
Conversation
|
It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the |
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughThe release notes for Home Assistant 2025.6 were revised for improved clarity, tone, and phrasing across multiple sections. Titles and descriptions were updated, explanations expanded, and guidance clarified, focusing on Bluetooth, pickers, integrations, dashboard, deprecations, sidebar customization, and media player features. No functional changes were made. Changes
Sequence Diagram(s)No sequence diagram generated as the changes are limited to documentation wording and structure. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
source/_posts/2025-06-11-release-20256.markdown (3)
111-116: Use consistent emphasis style
The asterisk-based emphasis (everywhere) conflicts with the project’s underscore convention. Consider changing to_everywhere_for consistency with other Markdown in this file.🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
111-111: Emphasis style
Expected: underscore; Actual: asterisk(MD049, emphasis-style)
111-111: Emphasis style
Expected: underscore; Actual: asterisk(MD049, emphasis-style)
121-131: Tighten phrasing in Bluetooth section
- Replace “with the use of something like [ESPHome Bluetooth proxies]” with “using [ESPHome Bluetooth proxies]” to eliminate unnecessary words.
- Simplify “It not only shows the actively connected devices, but also the devices that are in range, but not yet known to Home Assistant” to “It shows both actively connected devices and in-range devices not yet known to Home Assistant.”
364-367: Rephrase sidebar improvements for clarity and tone
The current lines use exclamations, colloquialisms (“magically”), and an emoji, which reduce formality. Consider a more streamlined version, for example:-The biggest improvement is actually found somewhere else! Previously, the customization of the sidebar was only applied to the device you made the changes on; and even more annoying, sometimes it would lose the changes, or it would magically forget your settings on our [mobile companion apps] when you switched between your home network (and thus the internal URL). 🥲 +Previously, sidebar customizations were only applied to the device on which they were made and could be lost when switching networks (e.g., in the [mobile companion apps]). -In this release, this annoyance has been fixed! The sidebar customization is now stored in your user profile, so your personalized layout follows you across all devices you use with Home Assistant! +In this release, we’ve resolved this issue: sidebar customizations are now stored in your user profile and follow you across all devices.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting
📒 Files selected for processing (1)
source/_posts/2025-06-11-release-20256.markdown(4 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/_posts/2025-06-11-release-20256.markdown
111-111: Emphasis style
Expected: underscore; Actual: asterisk
(MD049, emphasis-style)
111-111: Emphasis style
Expected: underscore; Actual: asterisk
(MD049, emphasis-style)
🪛 LanguageTool
source/_posts/2025-06-11-release-20256.markdown
[style] ~370-~370: Qualifiers like “somewhat” can weaken your message and make your writing sound uncertain. Consider removing it or choosing an alternative to sound more confident.
Context: ... they are in. However, this feature was somewhat limited, as it could only be used as ac...
(SOMEWHAT)
🔇 Additional comments (2)
source/_posts/2025-06-11-release-20256.markdown (2)
3-3: Title is clear and descriptive
The updated title “2025.6: Getting picky about Bluetooth” is concise and more engaging than the previous generic label.
93-93: TOC entry matches updated header
Renaming the entry to “Clearer Bluetooth networks” aligns accurately with the section title and improves consistency.
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (3)
source/_posts/2025-06-11-release-20256.markdown (3)
111-111: Use consistent Markdown emphasis style
markdownlint expects underscores for emphasis. Replace*everywhere*with_everywhere_to adhere to style guidelines.- Pickers are *everywhere* in Home Assistant + Pickers are _everywhere_ in Home Assistant🧰 Tools
🪛 markdownlint-cli2 (0.17.2)
111-111: Emphasis style
Expected: underscore; Actual: asterisk(MD049, emphasis-style)
111-111: Emphasis style
Expected: underscore; Actual: asterisk(MD049, emphasis-style)
370-370: Strengthen wording by removing qualifier
“Somewhat limited” weakens the message. Consider removing “somewhat” for a more confident tone.- However, this feature was somewhat limited, as it could only be used as actions within things like automations or scripts. + However, this feature was limited, as it could only be used as actions within automations or scripts.🧰 Tools
🪛 LanguageTool
[style] ~370-~370: Qualifiers like “somewhat” can weaken your message and make your writing sound uncertain. Consider removing it or choosing an alternative to sound more confident.
Context: ... they are in. However, this feature was somewhat limited, as it could only be used as ac...(SOMEWHAT)
378-378: Fix comma usage after “note that”
Remove the extraneous comma for smoother readability.- Please note that, you can only join or unjoin groups of media players that support this feature. + Please note that you can only join or unjoin groups of media players that support this feature.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting
📒 Files selected for processing (1)
source/_posts/2025-06-11-release-20256.markdown(4 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/_posts/2025-06-11-release-20256.markdown
111-111: Emphasis style
Expected: underscore; Actual: asterisk
(MD049, emphasis-style)
111-111: Emphasis style
Expected: underscore; Actual: asterisk
(MD049, emphasis-style)
🪛 LanguageTool
source/_posts/2025-06-11-release-20256.markdown
[style] ~370-~370: Qualifiers like “somewhat” can weaken your message and make your writing sound uncertain. Consider removing it or choosing an alternative to sound more confident.
Context: ... they are in. However, this feature was somewhat limited, as it could only be used as ac...
(SOMEWHAT)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Redirect rules - home-assistant-docs
- GitHub Check: Header rules - home-assistant-docs
- GitHub Check: Pages changed - home-assistant-docs
🔇 Additional comments (20)
source/_posts/2025-06-11-release-20256.markdown (20)
3-3: Title updated to reflect Bluetooth focus
The new title “2025.6: Getting picky about Bluetooth” aligns with the content theme and improves reader engagement.
93-93: TOC entry matches updated heading
The “Making sense of Bluetooth” link now accurately reflects the revised Bluetooth section heading.
113-113: Clarified previous entity picker reference
The sentence about last release’s entity picker is concise and informative.
115-115: Expanded search experience coverage
Good emphasis on consistency across all picker types.
121-121: Bluetooth section heading updated
“Making sense of Bluetooth” is more engaging than the generic previous title.
123-123: Introductory Bluetooth capabilities description
Clear and to the point.
125-125: Visualization feature description is concise
Well-structured explanation of the new Bluetooth integration visualization.
129-129: Clarified in-range device visibility
Good note about discovering devices not yet known to Home Assistant.
131-131: Cross-integration consistency highlighted
Excellent call-out about aligning Zigbee’s visualization style.
139-139: Experimental dashboard intro refined
The April release reference sets context nicely for iterative improvements.
141-141: Iteration process emphasized
“Continuously iterated on” effectively conveys the experimental nature.
143-143: New “Actions” section description
Clear listing of added entity types enhances reader understanding.
145-145: Section renaming clarification
Renaming “Entertainment” to “Media players” improves clarity on purpose.
152-152: Deprecation overview sets reader expectations
Good introductory context for upcoming deprecations.
153-153: Installation methods deprecation clear
Explicitly calling out Core and Supervised methods is helpful for affected users.
155-155: 32-bit architectures deprecation clearly stated
The rationale and impacted architectures are well documented.
157-157: Repair issue guidance is actionable
Informing users about the repair dashboard notification aids migration readiness.
159-159: Support timeline communicated effectively
Clear six‐month support window gives users time to plan migration.
364-364: Sidebar improvement narrative flows
Good setup explaining prior annoyance before presenting the fix.
366-366: Persistent user‐profile storage highlighted
Storing customization in the user profile addresses the key pain point.
Proposed change
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.Summary by CodeRabbit