8000 2025.2.1 by frenck · Pull Request #37353 · home-assistant/home-assistant.io · GitHub
[go: up one dir, main page]

Skip to content

2025.2.1 #37353

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

2025.2.1 #37353

merged 1 commit into from
Feb 7, 2025

Conversation

frenck
Copy link
Member
@frenck frenck commented Feb 7, 2025

Proposed change

Release notes for 2025.2.1
home-assistant/core#137688

Summary by CodeRabbit

  • New Features

    • Added a dedicated "Patch Releases" section in the release notes to communicate the plan for regular weekly bug fix updates.
  • Bug Fixes

    • Implemented numerous fixes across integrations, enhancing overall stability and improving error handling and configuration flows.
  • Chores

    • Updated the release version and release date information to reflect the new patch update.

@frenck frenck added the blog This PR adds a blog article to the Home Assistant website label Feb 7, 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 Feb 7, 2025
@home-assistant
Copy link
home-assistant bot commented Feb 7, 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.

Copy link
netlify bot commented Feb 7, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 866889b
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/67a639b961289e00085b79d3
😎 Deploy Preview https://deploy-preview-37353--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 7, 2025
📝 Walkthrough

Walkthrough

This pull request updates Home Assistant’s release documentation and configuration. The configuration file now reflects a bumped patch version (from 0 to 1) along with an updated release date (from February 5 to February 7, 2025). Additionally, the release notes and core changelog have been enhanced; they now include a new “Patch releases” section detailing the 2025.2.1 release—with a focus on bug fixes, dependency upgrades, and integration adjustments.

Changes

File(s) Change Summary
_config.yml Updated patch version from 0 to 1 and revised release date from 2025-02-05 to 2025-02-07.
source/_posts/...release-20252.markdown
source/changelogs/...core-2025.2.markdown
Added patch release documentation for 2025.2.1 (February 7): introduced a new "Patch releases" section in the release notes and updated the core changelog with dependency bumps and integration fixes.

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 (3)
source/_posts/2025-02-05-release-20252.markdown (2)

478-515: New Patch Releases Section Review: The newly added "Patch releases" section—including the "2025.2.1 - February 7" subsection and itemized bullet list—provides clear, detailed release notes for this patch. Please double-check that the listed fixes, dependency bumps, and related links precisely reflect the changes intended for the 2025.2.1 release and that the formatting remains consistent with the rest of the document. Optionally, consider adding a brief lead-in sentence before the bullet list for enhanced context.


518-568: Cleanup Reference Definitions: Markdownlint reports several duplicate/unused link and image reference definitions (e.g. for “#137448”, “@allenporter”, “@frenck”, etc.). It would improve readability and compliance with MD053 if you remove or consolidate these references.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


567-567: 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 (1)

1395-1395: Remove Unused Link Reference Definition

The static analysis tool flagged an unused link reference definition (“#137448”). Since it does not appear to be referenced anywhere in the document, please remove it to improve clarity and avoid confusion.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

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

(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 dbd40cb and 866889b.

📒 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

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

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

(MD053, link-image-reference-definitions)

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

74-75: Table of Contents Anchor Check: Please verify that the new TOC entries for “Patch releases” and “2025.2.1 - February 7” correctly link to the corresponding sections. Ensure that the generated slugs (e.g. “#patch-releases” and “#202521---february-7”) match the header IDs produced by your markdown renderer.

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

1361-1392: Review of the Release Notes Content

The new release section for "Release 2025.2.1 - February 7" is clear and comprehensive. All the bullet items explain specific fixes, bumps, and behavioral changes with clear attribution and pull request references. Please double-check that the details (e.g. version numbers and brief item descriptions) match the intended changes from the linked PRs. Overall, the release note entries appear well organized and provide good context for users.

@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Feb 7, 2025
@frenck frenck merged commit 6db0b9a into current Feb 7, 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 Feb 7, 2025
@frenck frenck deleted the frenck-2025-0048 branch February 7, 2025 18:36
CrEaK pushed a commit to CrEaK/home-assistant.io that referenced this pull request Feb 8, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Feb 8, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0