Skip to content

2025.1.4 #37084

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

2025.1.4 #37084

merged 1 commit into from
Jan 24, 2025

Conversation

frenck
Copy link
Member

@frenck frenck commented Jan 24, 2025

Proposed change

Release notes for home-assistant/core#136407

Summary by CodeRabbit

  • New Release
    • Home Assistant version 2025.1.4 released on January 24
    • Updates to Hydrawise integration
    • Improvements to holidays library
    • Enhancements in thumbnail URL handling
    • Bug fixes for APCUPSD, LinkPlay, Peblar, and MyUplink integrations
    • Frontend and library version updates

@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 Jan 24, 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 Jan 24, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit cb6da0e
🔍 Latest deploy log https://app.netlify.com/sites/home-assistant-docs/deploys/6793516b55f5ad000809c076
😎 Deploy Preview https://deploy-preview-37084--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 Jan 24, 2025

📝 Walkthrough

Walkthrough

The pull request introduces updates to Home Assistant version 2025.1, specifically patch release 2025.1.4 scheduled for January 24. The changes involve configuration updates in _config.yml, adding a new release section in the release markdown file, and documenting core updates in the changelog. The modifications encompass various integration improvements, library updates, and bug fixes across multiple components of the Home Assistant platform.

Changes

File Change Summary
_config.yml - Incremented current_patch_version from 3 to 4
- Updated date_released to 2025-01-24
source/_posts/2025-01-03-release-20251.markdown - Added new patch release section for 2025.1.4 on January 24
source/changelogs/core-2025.1.markdown - Added new release section for Core version 2025.1.4
- Documented updates to Hydrawise, Holidays library, thumbnail handling, APCUPSD, LinkPlay, Peblar, and MyUplink integrations
- Updated frontend and various library versions

Sequence Diagram

sequenceDiagram
    participant Config as _config.yml
    participant ReleasePost as Release Markdown
    participant Changelog as Core Changelog
    
    Config->>Config: Update patch version
    Config->>Config: Update release date
    
    ReleasePost->>ReleasePost: Add 2025.1.4 release details
    
    Changelog->>Changelog: Document Core version updates
    
    Changelog-->>ReleasePost: Synchronize release information
Loading

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2377f05 and cb6da0e.

📒 Files selected for processing (3)
  • _config.yml (1 hunks)
  • source/_posts/2025-01-03-release-20251.markdown (2 hunks)
  • source/changelogs/core-2025.1.markdown (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • _config.yml
🧰 Additional context used
🪛 Markdownlint (0.37.0)
source/_posts/2025-01-03-release-20251.markdown

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)

source/changelogs/core-2025.1.markdown

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(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 (4)
source/_posts/2025-01-03-release-20251.markdown (3)

842-843: LGTM!

The patch release header follows the established format and maintains consistency with other patch releases.


844-856: LGTM!

The list of changes is well-documented with:

  • Clear descriptions of the changes
  • Proper attribution to authors
  • Consistent linking to pull requests

857-881: LGTM! Duplicate link definitions are expected.

The reference-style links are properly formatted. The duplicate link definitions flagged by markdownlint are intentional and necessary for maintaining consistent author links across multiple patch releases in the same file.

Safely ignoring the markdownlint warnings about duplicate link definitions as they are false positives in this context.

🧰 Tools
🪛 Markdownlint (0.37.0)

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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)


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

(MD053, link-image-reference-definitions)

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

1290-1304: LGTM! The changelog entry for 2025.1.4 is well-documented.

The changes are properly formatted, clearly describe the updates, and include appropriate attribution to contributors. The changelog effectively communicates the key changes in this release.


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.

@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Jan 24, 2025
@frenck frenck merged commit f60e27c into current Jan 24, 2025
9 checks passed
@home-assistant home-assistant bot removed 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 parent-merged The parent PR has been merged already labels Jan 24, 2025
@frenck frenck deleted the frenck-2025-0044 branch January 24, 2025 08:51
@github-actions github-actions bot locked and limited conversation to collaborators Jan 25, 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.

2 participants