Skip to content
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

2025.2.2 #37404

Merged
merged 1 commit into from
Feb 10, 2025
Merged

2025.2.2 #37404

merged 1 commit into from
Feb 10, 2025

Conversation

frenck
Copy link
Member

@frenck frenck commented Feb 10, 2025

Proposed change

home-assistant/core#138231 (comment)

Summary by CodeRabbit

  • Chores

    • Updated Home Assistant's patch version and release date to reflect the latest update, ensuring accurate system versioning for users.
  • New Features

    • Introduced a dedicated patch release section (2025.2.2) highlighting integration enhancements such as a new endpoint and improved configuration handling to boost functionality.
  • Bug Fixes

    • Addressed various issues impacting device setup, update speeds, and overall integration reliability. These fixes ensure smoother operation and a more stable experience for Home Assistant users.

@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 10, 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 10, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 810fe81
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/67aa64c9aeb14a000838429f
😎 Deploy Preview https://deploy-preview-37404--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 10, 2025

📝 Walkthrough

Walkthrough

This pull request updates the Home Assistant patch release details. The configuration file is modified to increment the patch version and adjust the release date. Additionally, both the release notes and the core changelog now include a new section for patch release 2025.2.2, which details new endpoints, integration improvements, bug fixes, and dependency version bumps. The updates cover various integrations, including Google Drive (with changes like a backup listener call and resumable uploads) and LaCrosse View, among others.

Changes

Files Change Summary
_config.yml Incremented current_patch_version from 1 to 2 and updated date_released from 2025-02-07 to 2025-02-10.
source/_posts/...release-20252.markdown, source/changelogs/...2025.2.markdown Added a new patch release section (2025.2.2 - February 10, 2025) with details on new endpoints (e.g., LaCrosse View), conversion fixes (Coinbase amounts), Google Drive integration improvements (backup listener and resumable uploads), various integration fixes (LG webOS TV, Onkyo, TP-Link, etc.), and dependency version bumps.

Sequence Diagram(s)

sequenceDiagram
    participant Config as _config.yml
    participant Release as Release Docs
    participant Integration as Integration Service
    participant GD as Google Drive
    participant LV as LaCrosse View

    Config->>Release: Update patch version and release date
    Release->>Integration: Publish new patch release details
    Integration->>GD: Initiate backup listener during setup
    GD-->>Integration: Acknowledge resumable uploads enabled
    Integration->>LV: Activate new endpoint for LaCrosse View
    LV-->>Integration: Process endpoint request
Loading

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

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

603-653: Duplicate Link/Image Reference Definitions

Static analysis has flagged several duplicate link or image reference definitions (e.g. for “#137448”, “#137688”, “@allenporter”, “@andrewsayre”, “@bdraco”, “@bieniu”, “@cdce8p”, “@emontnemery”, “@frenck”, “@thecode”, “@tr4nt0r”, “@tronikos”, “@zweckj”). These duplicates can be consolidated to improve clarity and maintainability of the markdown source. Although they may not affect the rendered output, cleaning them up helps avoid potential conflicts and reduces noise in the document.

Tags:

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)

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

1457-1457: Clarify Conditional Expression

The bullet item:

"Use the external URL set in Settings > System > Network if my is disabled as redirect URL for Google Drive instructions"

contains an ambiguous phrase “if my is disabled.” Please clarify what “my” refers to – perhaps it is a typographical error (e.g. should it read “if HA is disabled” or “if MDNS is disabled”?)


1479-1529: Markdown Reference Definitions Cleanup

Static analysis tools have flagged several duplicate markdown link or image reference definitions (e.g. duplicate entries for “#137448”, “@allenporter”, “@andrewsayre”, “@bdraco”, “@bieniu”, “@cdce8p”, “@emontnemery”, “@frenck”, “@thecode”, “@tr4nt0r”, “@zweckj”). Please review these duplicate reference definitions and remove any redundancies to improve maintainability and comply with MD053 guidelines.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


1529-1529: 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 2e74958 and 810fe81.

📒 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

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)

source/changelogs/core-2025.2.markdown

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)

🔇 Additional comments (21)
source/_posts/2025-02-05-release-20252.markdown (1)

570-600: New Patch Release Section – 2025.2.2 Update

This section clearly introduces the new patch release with its scheduled date (February 10, 2025) and lists the associated changes. Please verify that each list item (e.g. “LaCrosse View new endpoint”, “Convert coinbase account amounts as floats”, etc.) accurately reflects the intended updates and corresponds with the changelog details in source/changelogs/core-2025.2.markdown.

Tags:

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

1446-1447: New Release Section Header Approved

The header “## Release 2025.2.2 - February 10” is clear and follows the expected format for a new patch release section.


1448-1453: Bullet Items (Lines 1448–1453) Overview

The initial bullet items – including the new LaCrosse View endpoint, conversion of coinbase account amounts to floats, and version bumps for ohmepy and onedrive_personal_sdk, as well as the integration domain limitations for Habitica and Nordpool – are clearly presented and consistent with our changelog style.


1454-1456: Bullet Items (Lines 1454–1456) Verification

These items, which address limiting the transmission ConfigEntrySelect to the integration domain, fixing tplink child update delays, and initiating the backup listener during Google Drive setup, are well stated and match the release note conventions.


1458-1458: Manufacturer ID Matching

The bullet “Fix manufacturer_id matching for 0” is concise and clear.


1459-1459: Onkyo DAB Radio Fix

The bullet “Fix DAB radio in Onkyo” is straightforward.


1460-1460: LG webOS TV Setup Issue

The bullet “Fix LG webOS TV fails to setup when device is off” is clear and appears correct.


1461-1461: Heos Migration

The bullet “Fix heos migration” is succinct and acceptable.


1462-1462: Pydrawise Version Bump

The bullet “Bump pydrawise to 2025.2.0” meets our expectations for version bump items.


1463-1463: aioshelly Version Bump

The bullet “Bump aioshelly to version 12.4.2” is clear.


1464-1464: Telegram Crash Prevention

The bullet “Prevent crash if telegram message failed and did not generate an ID” is clear and valuable for stability.


1465-1465: Habiticalib Version Bump

The bullet “Bump habiticalib to v0.3.7” is straightforward.


1467-1467: Resumable Uploads in Google Drive

The bullet “Use resumable uploads in Google Drive” is clear and follows best practices.


1468-1468: py-synologydsm-api Version Bump

The bullet “Bump py-synologydsm-api to 2.6.2” is clear.


1469-1469: Generic Agent Exceptions Handling

The bullet “Handle generic agent exceptions when getting and deleting backups” is clear and addresses robustness.


1470-1470: Onedrive-Personal-SDK Version Bump

The bullet “Bump onedrive-personal-sdk to 0.0.10” is acceptable.


1471-1471: Backup Retention Policy

The bullet “Keep one backup per backup agent when executing retention policy” is clear.


1472-1472: Inexogy Logging Improvement

The bullet “Improve inexogy logging when failed to update” is concise and clear.


1473-1473: Pyheos Version Bump

The bullet “Bump pyheos to v1.0.2” is acceptable.


1474-1474: Frontend Version Update

The bullet “Update frontend to 20250210.0” is clear and reflects the new release date/version.


1475-1475: Lacrosse-View Version Bump

The bullet “Bump lacrosse-view to 1.1.1” is clear.

@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Feb 10, 2025
@frenck frenck merged commit 9c54d5a into current Feb 10, 2025
9 checks passed
@frenck frenck deleted the frenck-2025-0054 branch February 10, 2025 21:10
@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 Feb 10, 2025
CrEaK pushed a commit to CrEaK/home-assistant.io that referenced this pull request Feb 11, 2025
CrEaK pushed a commit to CrEaK/home-assistant.io that referenced this pull request Feb 11, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Feb 11, 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