Skip to content

2025.4.3 #38632

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.

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

Merged
merged 1 commit into from
Apr 19, 2025
Merged

2025.4.3 #38632

merged 1 commit into from
Apr 19, 2025

Conversation

frenck
Copy link
Member

@frenck frenck commented Apr 19, 2025

Proposed change

Release notes for 2025.4.3

home-assistant/core#143253

Summary by CodeRabbit

  • Bug Fixes

    • Resolved issues across multiple integrations, including duke_energy, Tessie, home_connect, Habitica, MQTT, Squeezebox, Apple TV, Reolink, Comelit, Shelly, Starlink, and SmartThings.
    • Improved reliability and accuracy for device discovery, data retrieval, and sensor updates.
  • Improvements

    • Enhanced quality in LLM conversation agent responses and Kraken integration filtering.
    • Updated URLs and optimized schema handling for certain integrations.
  • Dependency Updates

    • Bumped several libraries to newer versions for improved stability and compatibility.
  • Documentation

    • Updated release notes and changelog with detailed information about the latest patch release.

@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 19, 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.

Copy link

netlify bot commented Apr 19, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 2757ded
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/68036b3cab4296000866ac7e
😎 Deploy Preview https://deploy-preview-38632--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.

Copy link
Contributor

coderabbitai bot commented Apr 19, 2025

📝 Walkthrough

Walkthrough

The changes introduce a new patch release, version 2025.4.3, for Home Assistant. The configuration file was updated to reflect the new version number and release date. The changelog and release notes were expanded to include details about this patch, which addresses various bug fixes, dependency updates, and improvements across multiple integrations and components. No changes were made to public APIs or exported entities; all updates are related to documentation and release metadata.

Changes

File(s) Change Summary
_config.yml Updated Home Assistant version from 2025.4.2 to 2025.4.3 and changed the release date from April 12, 2025, to April 19, 2025.
source/_posts/2025-04-02-release-20254.markdown Added a new section for patch release 2025.4.3 (April 19) to the release notes, detailing bug fixes, dependency bumps, and improvements for various integrations (e.g., duke_energy, Tessie, home_connect, Habitica, MQTT, Squeezebox, Apple TV, Reolink, LLM conversation agent, Kraken, Environment Canada, devolo_plc_api, holidays, pysmhi, ZHA, Jewish calendar, UK Transport, Comelit, Shelly, Python-2.0, Starlink, SmartThings). Included associated pull request links and contributor references.
source/changelogs/core-2025.4.markdown Added a "2025.4.3 - April 19" section to the changelog, listing all fixes, improvements, and library version bumps included in the patch release, along with references to related pull requests and contributors. No changes to public or exported entities.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Documentation
    participant Config
    participant ReleaseNotes

    User->>Documentation: View changelog/release notes
    Documentation->>Config: Retrieve current version and release date
    Documentation->>ReleaseNotes: Display details for 2025.4.3
    ReleaseNotes-->>User: Show bug fixes, improvements, dependency bumps, PR links, contributors
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.

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.

❤️ Share
🪧 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 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.

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: 1

🔭 Outside diff range comments (1)
_config.yml (1)

117-117: 🛠️ Refactor suggestion

Add link to patch release notes
The patch_version_notes is still empty. To enable the site’s “Latest release notes” link, update it to the anchor for the 2025.4.3 blog post (e.g., "#202543---april-19").

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6f6c5cd and 2757ded.

📒 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/_posts/2025-04-02-release-20254.markdown

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


773-773: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@gjohansson-ST"

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)

source/changelogs/core-2025.4.markdown

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


1215-1215: Link and image reference definitions should be needed
Duplicate link or image reference definition: "@gjohansson-ST"

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)

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

111-112: Release metadata updated correctly
The current_patch_version and date_released fields have been bumped to 3 and 2025-04-19, respectively, matching the new patch release.

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

73-73: Include 2025.4.3 in the patch releases list
The navigation entry for 2025.4.3 - April 19 has been correctly added to the “Patch releases” section. Ensure the anchor link matches the heading ID generated for this new entry.

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

1147-1173: Add section for patch release 2025.4.3
The new “2025.4.3 – April 19” patch section and its list of fixes, dependency bumps, and other improvements have been added correctly. Entries match the core PR #143253 details.

Comment on lines +1176 to +1180
[#141505]: https://github.com/home-assistant/core/pull/141505
[#142299]: https://github.com/home-assistant/core/pull/142299
[#142510]: https://github.com/home-assistant/core/pull/142510
[#142666]: https://github.com/home-assistant/core/pull/142666
[#142755]: https://github.com/home-assistant/core/pull/142755
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Remove duplicate link and reference definitions
There are multiple duplicate reference definitions ([#141505], [#142299], [#142755], and duplicate author tags like @bre77, @allenporter, etc.) in the link-definition blocks. These will collide in Markdown and should be deduplicated.

Suggested diff to clean up the definitions (remove redundant blocks):

- [#141505]: https://github.com/home-assistant/core/pull/141505
- [#142299]: https://github.com/home-assistant/core/pull/142299
- [#142755]: https://github.com/home-assistant/core/pull/142755
...
- [@bre77]: https://github.com/Bre77
- [@allenporter]: https://github.com/allenporter
- [@chemelli74]: https://github.com/chemelli74
...

Ensure each reference appears only once in the entire file.

Also applies to: 1204-1220

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)

@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Apr 19, 2025
@frenck frenck merged commit c51b56e into current Apr 19, 2025
9 checks passed
@frenck frenck deleted the frenck-2025-0188 branch April 19, 2025 10:23
@home-assistant home-assistant bot removed needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch parent-merged The parent PR has been merged already in-progress This PR/Issue is currently being worked on labels Apr 19, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Apr 20, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
current This PR goes into the current branch has-parent This PR has a parent PR in a other repo
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant