Skip to content

2025.4.2 #38493

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Apr 12, 2025
Merged

2025.4.2 #38493

merged 3 commits into from
Apr 12, 2025

Conversation

frenck
Copy link
Member

@frenck frenck commented Apr 11, 2025 •
edited by coderabbitai bot
Loading

Proposed change

Release notes for home-assistant/core#142755

Summary by CodeRabbit

  • Chores
    • Updated release version and release date to reflect the new patch release.
  • New Features
    • Introduced a new sensor integration for CO₂ monitoring.
    • Added an enhanced option for Google search functionality.
  • Bug Fixes
    • Improved error handling for calendar events and map updates.
    • Resolved issues with device initialization, state reporting, and several integrations for a smoother overall experience.
    • Enhanced handling of Google Generative AI responses and MQTT config validation.

@frenck frenck added the blog This PR adds a blog article to the Home Assistant website label Apr 11, 2025
@home-assistant home-assistant bot added current This PR goes into the current branch has-parent This PR has a parent PR in a other repo in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch labels Apr 11, 2025
@home-assistant
Copy link

It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the next branch. Please change the target branch of this PR to next and rebase if needed.

@frenck frenck mentioned this pull request Apr 11, 2025
Merged
@netlify Netlify
Copy link

netlify bot commented Apr 11, 2025 •
edited
Loading

✅ Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 9d51130
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/67fa37328181610008a7e001
😎 Deploy Preview https://deploy-preview-38493--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 11, 2025 •
edited
Loading

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

This update increments the Home Assistant patch version and revises the release date in the configuration. Additionally, new release notes for patch version 2025.4.2 have been added, consolidating various fixes and enhancements. The release notes detail dependency bumps, improved error handling in the remote calendar flow, checks for the existence of the Roborock map before updates, and the introduction of new configuration options and sensor classes.

Changes

File(s) Change Summary
_config.yml Updated Home Assistant release details: current_patch_version incremented from 1 to 2; date_released changed from 2025-04-04 to 2025-04-12.
source/_posts/...release-20254.markdown, source/changelogs/core-2025.4.markdown Added a new patch release section (2025.4.2 – April 12) including enhancements and bug fixes. Changes cover dependency bumps (e.g., opower, flux_led, aioesphomeapi), improved error handling (remote calendar flow, Roborock map checks, MQTT logging), and new configurations (SensorDeviceClass, enable_google_search_tool).

Sequence Diagram(s)

sequenceDiagram
    participant HA as Home Assistant
    participant RC as Remote Calendar Service
    participant Logger
    HA->>RC: Request calendar update
    alt Successful Response
        RC-->>HA: Updated calendar data
    else Error Occurs
        RC-->>HA: Error details
        HA->>Logger: Log error details
    end
Loading 
sequenceDiagram
    participant RI as Roborock Integration
    participant RM as Map Checker
    participant Logger
    RI->>RM: Verify current map existence
    alt Map exists
        RI->>RM: Update map state
    else Map missing
        RI->>Logger: Log warning/error message
    end
Loading

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.
📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1c05240 and 9d51130.

📒 Files selected for processing (1)
  • source/_posts/2025-04-02-release-20254.markdown (2 hunks)
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

coderabbitai[bot]
coderabbitai bot reviewed Apr 11, 2025
View reviewed changes
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
source/_posts/2025-04-02-release-20254.markdown (1)

626-634: Markdown Link References Cleanup (Optional):
Static analysis flags several duplicate or unused reference definitions (e.g. “#141505”, “#142299”, “@IvanLH”, “@Lash-L”, etc.). While these may be false positives depending on how reference linking is used in the document, consider cleaning them up to improve overall markdown quality and eliminate warnings from markdownlint.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

626-626: Link and image reference definitions should be needed
Duplicate link or image reference definition: "#141505"

(MD053, link-image-reference-definitions)

629-629: Link and image reference definitions should be needed
Unused link or image reference definition: "#142299"

(MD053, link-image-reference-definitions)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4836394 and 5795636.

📒 Files selected for processing (3)
  • _config.yml (1 hunks)
  • source/_posts/2025-04-02-release-20254.markdown (2 hunks)
  • source/changelogs/core-2025.4.markdown (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/changelogs/core-2025.4.markdown

1068-1068: Link and image reference definitions should be needed
Duplicate link or image reference definition: "#141505"

(MD053, link-image-reference-definitions)

1071-1071: Link and image reference definitions should be needed
Unused link or image reference definition: "#142299"

(MD053, link-image-reference-definitions)

1115-1115: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@IvanLH"

(MD053, link-image-reference-definitions)

1123-1123: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@bdraco"

(MD053, link-image-reference-definitions)

1125-1125: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@bramkragten"

(MD053, link-image-reference-definitions)

1126-1126: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@chemelli74"

(MD053, link-image-reference-definitions)

1128-1128: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@fredrike"

(MD053, link-image-reference-definitions)

1129-1129: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@frenck"

(MD053, link-image-reference-definitions)

1132-1132: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@joostlek"

(MD053, link-image-reference-definitions)

1134-1134: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@marcelveldt"

(MD053, link-image-reference-definitions)

1136-1136: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@puddly"

(MD053, link-image-reference-definitions)

source/_posts/2025-04-02-release-20254.markdown

626-626: Link and image reference definitions should be needed
Duplicate link or image reference definition: "#141505"

(MD053, link-image-reference-definitions)

629-629: Link and image reference definitions should be needed
Unused link or image reference definition: "#142299"

(MD053, link-image-reference-definitions)

673-673: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@IvanLH"

(MD053, link-image-reference-definitions)

675-675: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@Lash-L"

(MD053, link-image-reference-definitions)

677-677: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@Thomas55555"

(MD053, link-image-reference-definitions)

680-680: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@andrewsayre"

(MD053, link-image-reference-definitions)

681-681: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@bdraco"

(MD053, link-image-reference-definitions)

682-682: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@bieniu"

(MD053, link-image-reference-definitions)

683-683: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@bramkragten"

(MD053, link-image-reference-definitions)

684-684: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@chemelli74"

(MD053, link-image-reference-definitions)

686-686: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@fredrike"

(MD053, link-image-reference-definitions)

687-687: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@frenck"

(MD053, link-image-reference-definitions)

689-689: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@jbouwh"

(MD053, link-image-reference-definitions)

690-690: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@joostlek"

(MD053, link-image-reference-definitions)

692-692: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@marcelveldt"

(MD053, link-image-reference-definitions)

693-693: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@mib1185"

(MD053, link-image-reference-definitions)

694-694: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@puddly"

(MD053, link-image-reference-definitions)

695-695: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@starkillerOG"

(MD053, link-image-reference-definitions)

697-697: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@tronikos"

(MD053, link-image-reference-definitions)

🔇 Additional comments (4)
_config.yml (1)

109-112: Update Release Configuration Values:
The patch update is reflected by raising the current_patch_version to 2 and updating the date_released to "2025-04-11". This well‐aligns with the new release schedule. Please double‐check that all related documentation is synchronized with these configuration changes.

source/changelogs/core-2025.4.markdown (1)

1021-1066: Patch Release Changelog – 2025.4.2 Details:
The new changelog block for the patch release 2025.4.2 is comprehensive and properly attributes the contributions. A couple of suggestions:
• There is a typo in the entry “Check that the current roboorck map exists before updating it.” (line ~1027); it should be corrected to “roborock”.
• Two later entries bump the opower library—first to 0.10.0 (line ~1025) and then to 0.11.1 (line ~1033). Please verify that this sequence is intentional and accurately reflects the intended dependency updates.

Overall, the entries are clear and correctly formatted with proper issue references and contributor attributions.

source/_posts/2025-04-02-release-20254.markdown (2)

72-73: Navigation Update for Patch Releases:
The table of contents now correctly includes a link for the new patch release – “2025.4.2 - April 11”. Please ensure the anchor (#202542---april-11) exactly matches the header later in the document for consistent navigation.

579-625: Detailed Patch Release Section – 2025.4.2:
This newly added section enumerates the changes comprehensively. In addition to the points noted in the changelog review:
• Please fix the typo “roboorck” to “roborock” in the corresponding bullet.
• The dual entries for upgrading opower (first to 0.10.0 then later to 0.11.1) should be verified to ensure they represent the intended incremental update.

Overall, the patch release notes are informative and provide valuable context for users upgrading Home Assistant.

coderabbitai[bot]
coderabbitai bot reviewed Apr 11, 2025
View reviewed changes
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
source/changelogs/core-2025.4.markdown (1)

1027-1027: Typo in Roborock Reference
At line 1027 the text reads “Check that the current roboorck map exists before updating it.” A simple typo should be fixed to “Roborock”.

- Check that the current roboorck map exists before updating it.
+ Check that the current Roborock map exists before updating it.
source/_posts/2025-04-02-release-20254.markdown (2)

628-632: Optional: Cleanup of Duplicate Markdown Link References
Static analysis flags many duplicate link/image reference definitions (e.g. for “#141505”, “@IvanLH”, “@Lash-L”, etc.). Although they do not affect functionality, cleaning them up would improve maintainability and readability of the file.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

628-628: Link and image reference definitions should be needed
Duplicate link or image reference definition: "#141505"

(MD053, link-image-reference-definitions)

632-632: Link and image reference definitions should be needed
Unused link or image reference definition: "#142299"

(MD053, link-image-reference-definitions)

700-702: Optional: Remove Redundant Link References
Similar to the above, there are duplicate link reference definitions (e.g. for “@tronikos” and others) that appear to be repeated. If these duplicates are not required by your markdown flavor or build tooling, consider consolidating them to reduce clutter.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

700-700: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@starkillerOG"

(MD053, link-image-reference-definitions)

702-702: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@tronikos"

(MD053, link-image-reference-definitions)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5795636 and 1c05240.

📒 Files selected for processing (3)
  • _config.yml (1 hunks)
  • source/_posts/2025-04-02-release-20254.markdown (2 hunks)
  • source/changelogs/core-2025.4.markdown (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • _config.yml
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/_posts/2025-04-02-release-20254.markdown

72-72: Link fragments should be valid
null

(MD051, link-fragments)

628-628: Link and image reference definitions should be needed
Duplicate link or image reference definition: "#141505"

(MD053, link-image-reference-definitions)

632-632: Link and image reference definitions should be needed
Unused link or image reference definition: "#142299"

(MD053, link-image-reference-definitions)

677-677: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@IvanLH"

(MD053, link-image-reference-definitions)

679-679: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@Lash-L"

(MD053, link-image-reference-definitions)

681-681: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@Thomas55555"

(MD053, link-image-reference-definitions)

684-684: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@andrewsayre"

(MD053, link-image-reference-definitions)

685-685: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@bdraco"

(MD053, link-image-reference-definitions)

686-686: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@bieniu"

(MD053, link-image-reference-definitions)

687-687: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@bramkragten"

(MD053, link-image-reference-definitions)

688-688: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@chemelli74"

(MD053, link-image-reference-definitions)

690-690: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@fredrike"

(MD053, link-image-reference-definitions)

691-691: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@frenck"

(MD053, link-image-reference-definitions)

693-693: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@jbouwh"

(MD053, link-image-reference-definitions)

694-694: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@joostlek"

(MD053, link-image-reference-definitions)

696-696: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@marcelveldt"

(MD053, link-image-reference-definitions)

697-697: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@mib1185"

(MD053, link-image-reference-definitions)

698-698: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@puddly"

(MD053, link-image-reference-definitions)

699-699: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@sanjay900"

(MD053, link-image-reference-definitions)

700-700: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@starkillerOG"

(MD053, link-image-reference-definitions)

702-702: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@tronikos"

(MD053, link-image-reference-definitions)

source/changelogs/core-2025.4.markdown

1070-1070: Link and image reference definitions should be needed
Duplicate link or image reference definition: "#141505"

(MD053, link-image-reference-definitions)

1074-1074: Link and image reference definitions should be needed
Unused link or image reference definition: "#142299"

(MD053, link-image-reference-definitions)

1119-1119: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@IvanLH"

(MD053, link-image-reference-definitions)

1127-1127: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@bdraco"

(MD053, link-image-reference-definitions)

1129-1129: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@bramkragten"

(MD053, link-image-reference-definitions)

1130-1130: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@chemelli74"

(MD053, link-image-reference-definitions)

1132-1132: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@fredrike"

(MD053, link-image-reference-definitions)

1133-1133: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@frenck"

(MD053, link-image-reference-definitions)

1136-1136: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@joostlek"

(MD053, link-image-reference-definitions)

1138-1138: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@marcelveldt"

(MD053, link-image-reference-definitions)

1140-1140: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@puddly"

(MD053, link-image-reference-definitions)

⏰ 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 (6)
source/changelogs/core-2025.4.markdown (4)

72-72: Inconsistent Release Date in Patch Release Link
In the list at line 72 the patch release “2025.4.2” is shown with the date “April 11” (i.e. “- 2025.4.2 - April 11”), but the detailed section header at line 1021 says “2025.4.2 – April 12”. Please verify which date is correct and update both places for consistency.

1021-1021: Title for New Patch Release
The section header “## Release 2025.4.2 - April 12” clearly sets the intended release date. Once the link label is fixed (see above), this header looks correct and aligns with the PR objective of updating the patch release notes.

1025-1033: Duplicate opower Bump Items
Two items mention updating opower: one “Bump opower to 0.10.0” at line 1025 and another “Bump opower to 0.11.1” at line 1033. According to the release summary the intended update is to version 0.11.1. Please verify whether 0.10.0 is an interim step that should be removed or if the items need consolidation so that only the final opower bump is listed.

1021-1068: Overall Patch Release Details for 2025.4.2
All the list items in this new patch release section from line 1021 through 1068 cover a wide range of dependency bumps, additional error handling and fixes – from remote calendar flow improvements to integration-specific tweaks. Aside from the two points mentioned above (the inconsistent date and duplicate opower updates), the descriptions are clear and correspond with the PR objectives.

source/_posts/2025-04-02-release-20254.markdown (2)

72-72: Mismatch in Patch Release Navigation Date
In the patch releases navigation at line 72 the link for “2025.4.2” shows the date as “April 11” while the detailed section later (line 579+) uses “April 12”. For consistency across the document and with the changelog file, please update the navigation link so that the correct date appears consistently.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

72-72: Link fragments should be valid
null

(MD051, link-fragments)

579-593: Detailed Patch Release Section for 2025.4.2
The new “### 2025.4.2 - April 12” section (starting around line 579) lists all the fixes and updates in a clear bullet‐point format. The items mirror those in the changelog. Aside from the issues already noted in the changelog review, this section reads well and reflects the intended improvements.

@home-assistant home-assistant bot marked this pull request as draft April 11, 2025 22:30
@github-project-automation github-project-automation bot moved this from Todo to In Progress in Documentation PRs Apr 11, 2025
@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Apr 12, 2025
@frenck @joostlek
Update source/_posts/2025-04-02-release-20254.markdown
9d51130 
Co-authored-by: Joost Lekkerkerker <joostlek@outlook.com>
@frenck frenck marked this pull request as ready for review April 12, 2025 10:12
@home-assistant home-assistant bot requested a review from joostlek April 12, 2025 10:12
@frenck frenck merged commit c3434cc into current Apr 12, 2025
8 of 9 checks passed
@frenck frenck deleted the frenck-2025-0174 branch April 12, 2025 10:12
@home-assistant home-assistant bot removed parent-merged The parent PR has been merged already needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch in-progress This PR/Issue is currently being worked on labels Apr 12, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in Documentation PRs Apr 12, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Apr 13, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

@joostlek joostlek Awaiting requested review from joostlek

Assignees

@frenck frenck

Labels
blog This PR adds a blog article to the Home Assistant website current This PR goes into the current branch has-parent This PR has a parent PR in a other repo
Projects
No open projects
Documentation PRs
Status: Done
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@frenck @joostlek