Skip to content

2025.4.1 #38386

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 2 commits into from
Apr 4, 2025
Merged

2025.4.1 #38386

merged 2 commits into from
Apr 4, 2025

Conversation

frenck
Copy link
Member

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

Proposed change

Release notes for: home-assistant/core#142299

Summary by CodeRabbit

  • Release Update

    • Announced the new patch release (version 2025.4.1) effective April 4, 2025, with updated release details.

  • Bug Fixes & Stability

    • Resolved issues affecting integration responsiveness and connectivity, including fixes for Daikin and Comelit integrations.
    • Improved overall system performance by addressing event handling and polling delays.

  • New Features & Enhancements

    • Introduced a preset mode for climate control in SmartThings integration.
    • Added a new section in documentation detailing the schedule for upcoming patch releases.

@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 4, 2025
@home-assistant
Copy link

home-assistant bot commented Apr 4, 2025

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 4, 2025
Merged
@netlify Netlify
Copy link

netlify bot commented Apr 4, 2025 •
edited
Loading

✅ Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit c8af4dd
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/67f03f0bde72860008a2e4b2
😎 Deploy Preview https://deploy-preview-38386--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 4, 2025 •
edited
Loading

📝 Walkthrough

Walkthrough

This pull request updates Home Assistant’s release information by modifying version and release date details in the configuration file and by adding new documentation entries for the patch release. The configuration file now reflects an increment in the current_patch_version and a revised date_released. Additionally, two markdown files have been updated to include a new patch release section (2025.4.1 – April 4) with detailed notes covering bug fixes, library version bumps, and textual clarifications.

Changes

File(s) Change Summary
_config.yml Updated release details: current_patch_version changed from 0 to 1, and date_released updated from 2025-04-02 to 2025-04-04.
source/_posts/...release-20254.markdown and source/changelogs/core-2025.4.markdown Added documentation for patch release 2025.4.1 – April 4. The blog post now includes a new "Patch releases" section with a subsection for the patch, while the changelog file introduces a detailed release section listing multiple bug fixes, integration updates, library version bumps, and minor textual changes for Home Assistant components.
🪧 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 4, 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 (2)
source/_posts/2025-04-02-release-20254.markdown (1)

527-571: Resolve Duplicate/Unused Link Reference Definitions

Static analysis hints have flagged several duplicate and unused link/image reference definitions (for example, duplicates for @diegorro98, @bdraco, @chemelli74, @joostlek, @piitaya, and @puddly, as well as an unused reference for @frenck). Consolidate these references where possible and remove any that are not needed to clean up the markdown.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

971-971: Remove Unused Link Reference

The link reference definition for “[#141505]” is detected as unused. To keep the file clean and avoid markdownlint warnings, consider removing this unused definition.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(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 69cd649 and fae8e0f.

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

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

source/changelogs/core-2025.4.markdown

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

(MD053, link-image-reference-definitions)

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

109-113: Release Details Update Verification

The patch release details have been updated correctly: the current_patch_version is now set to 1 and the date_released has been updated to 2025-04-04. Ensure that these values remain consistent with your other release documentation (i.e. changelogs and posts).

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

70-71: Table of Contents Update for Patch Releases

A new entry for "Patch releases" and its subsection "2025.4.1 - April 4" have been added to the Table of Contents. Please verify that the corresponding anchor links (e.g. #patch-releases and #202541---april-4) resolve correctly on the rendered page.

496-550: Patch Releases Section Clarity

The newly added "Patch releases" section is well formatted and clearly lists all the fixes and improvements for the 2025.4.1 patch release. It provides detailed notes with pull request references and contributor links. Verify that all links (e.g., pull request numbers and contributor usernames) resolve as expected in the final rendered version.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD053, link-image-reference-definitions)

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

945-969: Clear and Concise Patch Release Notes

The new "Release 2025.4.1 - April 4" section is well structured. Each bullet point clearly summarizes the changes with appropriate contributor and PR references. Please double‑check that the descriptions exactly match the intended updates from the linked PRs.

coderabbitai[bot]
coderabbitai bot reviewed Apr 4, 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 (4)
source/changelogs/core-2025.4.markdown (2)

947-970: Bullet Points Consistency and Clarity:
All the bullet points in the new release section concisely enumerate bug fixes, version bumps, and improvements. Each item correctly references its corresponding pull request. One minor suggestion: in the bullet at line 948, you might consider rephrasing “Made Google Search enable dependent on Assist availability” to “Adjusted Google Search so that its availability depends on Assist” for improved clarity. Otherwise, the list is consistent and informative.

972-1020: Unused Link Reference Discovery:
The static analysis tool flags an unused link reference “#141505”. If this link is no longer required elsewhere in the document, please remove it to reduce clutter.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD053, link-image-reference-definitions)

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

70-71: Add Patch Releases Navigation Entry
The navigation now includes a “Patch releases” item with a subitem for “2025.4.1 - April 4.” This helps users quickly locate the new patch release notes. Please verify that the anchor IDs (i.e. #patch-releases and #202541---april-4) correctly match the section headings later in the document for proper in-page linking.

528-576: Review Link Reference Definitions
The file now includes extensive link reference definitions for pull requests and contributor handles; however, static analysis has flagged issues such as duplicate and possibly unused references (e.g., duplicate entries for [@joostlek], [@Petro31], etc.). To clean up markdownlint warnings and improve maintainability, please consider consolidating or removing redundant link definitions if they are not used in the document.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(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 fae8e0f and c8af4dd.

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

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

(MD053, link-image-reference-definitions)

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

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

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

(MD053, link-image-reference-definitions)

🔇 Additional comments (2)
source/changelogs/core-2025.4.markdown (1)

945-945: Release Title Verification:
The new release header “## Release 2025.4.1 - April 4” is clearly defined and appropriately formatted. Please verify that the version and the date (April 4) match the intended release details.

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

497-527: Introduce Patch Releases Section
A new “Patch releases” section has been added, including a detailed subsection for “2025.4.1 - April 4” with a list of fixes and improvements. The bullet list clearly outlines updates such as bug fixes, dependency bumps, and minor text corrections. Ensure that all pull request links and contributor references point to the correct resources, and that any reference IDs are up-to-date.

@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Apr 4, 2025
@frenck frenck merged commit 9a5da07 into current Apr 4, 2025
9 checks passed
@home-assistant home-assistant bot removed parent-merged The parent PR has been merged already 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 4, 2025
@frenck frenck deleted the frenck-2025-0173 branch April 4, 2025 21:00
@github-project-automation github-project-automation bot moved this from Todo to Done in Documentation PRs Apr 4, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Apr 5, 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

Assignees

@frenck frenck

Labels
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.
1 participant
@frenck