Skip to content

2025.2.5 #37612

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
Feb 21, 2025
Merged

2025.2.5 #37612

merged 1 commit into from
Feb 21, 2025

Conversation

frenck
Copy link
Member

@frenck frenck commented Feb 21, 2025

Proposed change

Release notes for: home-assistant/core#139012

Summary by CodeRabbit

  • New Features
    • Introduced release version 2025.2.5 with updated release details and release date.
    • Enhanced the Tuya Water Detector to support a new alarm state.
  • Bug Fixes
    • Fixed issues in preset mode settings and resolved sensor availability problems in integrations.
    • Addressed backup management errors, including filename handling and auto-backup validations.
    • Resolved playback issues for encrypted video files and improved hue effect handling.
  • Chores
    • Updated several dependencies and refreshed the frontend version.

@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 Feb 21, 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 Feb 21, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 605c838
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/67b8d6388213750008607f73
😎 Deploy Preview https://deploy-preview-37612--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 Feb 21, 2025

📝 Walkthrough

Walkthrough

The update increments the Home Assistant patch version and revises the release date in the configuration. A new release section for version 2025.2.5 is added across release notes and changelogs. The changes detail adjustments to the Tuya Water Detector alarm state, corrections in preset mode functionality, multiple library version bumps, sensor availability fixes, backup management improvements, state renaming from "returned" to "alert", and a frontend version update. The changelog file documents these fixes through newly added methods.

Changes

File(s) Change Summary
_config.yml Updated current_patch_version from 4 to 5 and date_released from 2025-02-14 to 2025-02-21.
source/_posts/2025-02-05-release-20252.markdown
source/.../core-2025.2.markdown
Added release notes for version 2025.2.5. Details include: adjustment to the Tuya Water Detector alarm state, bug fix in set_preset_mode_with_end_datetime, several library version bumps, sensor fixes for Opower integration, backup filename and settings corrections, state renaming ("returned" → "alert"), and a frontend version update. New methods documenting these changes were also introduced.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
  • @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: 0

🧹 Nitpick comments (4)
source/_posts/2025-02-05-release-20252.markdown (2)

742-772: New Release Section for 2025.2.5 Added
This section clearly introduces the new patch release notes for version 2025.2.5. The bullet points list various fixes, integrations updates, and version bumps – which nicely mirrors the details referenced in the associated core PR. Please verify that each change is accurately described and that all link references (e.g. pull request numbers) correctly resolve to the intended resources.


774-825: Markdown Link Reference Definitions – Duplicate Warning
Static analysis flagged several duplicate link/image reference definitions (for instance, [ #137448 ], [ #137688 ], [ #138231 ], etc.). These duplicate definitions might be intentional for clarity or reuse across multiple release sections. Please verify if they are needed; if not, consider consolidating them to simplify maintenance and adhere to markdown best practices.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)

source/changelogs/core-2025.2.markdown (2)

1647-1652: Duplicate and Unused Link Reference Definitions in PR References
Static analysis reports duplicate link reference definitions for several PR numbers (e.g. “#137448”, “#137688”, “#138231”, “#138408”) and flags an unused reference (“#138530”). If these definitions are not all required for clarity, or if they can be consolidated without losing any intended context, consider cleaning them up to improve the markdown’s maintainability.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


1684-1698: Duplicate Link Reference Definitions for Attribution References
There are additional duplicate link reference definitions—such as for “@bramkragten”, “@edenhaus”, “@emontnemery”, “@frenck”, “@mib1185”, “@shaiu”, “@starkillerOG”, and “@synesthesiam.” Please verify whether these duplications serve a specific purpose (for example, if the file is auto-generated) or if they could be consolidated to reduce redundancy in the documentation.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(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 f56b981 and 605c838.

📒 Files selected for processing (3)
  • _config.yml (1 hunks)
  • source/_posts/2025-02-05-release-20252.markdown (2 hunks)
  • source/changelogs/core-2025.2.markdown (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • _config.yml
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
source/_posts/2025-02-05-release-20252.markdown

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)

source/changelogs/core-2025.2.markdown

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(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 (1)
source/changelogs/core-2025.2.markdown (1)

1615-1645: New Release Section Added for 2025.2.5
The newly added release notes for version 2025.2.5 are clearly structured. Each bullet point concisely describes the changes—for example, adjusting the Tuya Water Detector alarm state to support “1,” fixing the typo in the preset mode function, bumping several integration versions (pyhive-integration, tesla-fleet-api, pysmarty2, pyvesync, etc.), renaming the “returned” state to “alert,” and addressing various backup-related and sensor fixes. Please double-check that every bullet accurately reflects the detailed changes from the corresponding PRs.

@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Feb 21, 2025
@frenck frenck merged commit 0660568 into current Feb 21, 2025
9 checks passed
@frenck frenck deleted the frenck-2025-0104 branch February 21, 2025 21:38
@home-assistant home-assistant bot removed 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 parent-merged The parent PR has been merged already labels Feb 21, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Feb 22, 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