Skip to content

Conversation

@agners
Copy link
Member

@agners agners commented Sep 18, 2025

Proposed change

Document when we declare an installation as unsupported due to outdated Home Assistant Core version.

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Supervisor (current branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Document when we declare an installation as unsupported due to outdated
Home Assistant Core version.
Copilot AI review requested due to automatic review settings September 18, 2025 13:14
@home-assistant home-assistant bot added the current This PR goes into the current branch label Sep 18, 2025
@netlify
Copy link

netlify bot commented Sep 18, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit 7a194db
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/68d29fabf1006f0008d7210a
😎 Deploy Preview https://deploy-preview-40914--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 project configuration.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds documentation explaining why Home Assistant installations become marked as unsupported when running outdated Core versions. The documentation explains the 24-month support policy and provides guidance for updating safely.

  • Documents the 24-month (approximately 24 releases) support policy for Home Assistant Core versions
  • Explains the impact of running unsupported versions (no updates for Core or add-ons)
  • Provides step-by-step guidance for safely updating outdated installations

@home-assistant home-assistant bot added has-parent This PR has a parent PR in another 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 Sep 18, 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.

sairon
sairon previously approved these changes Sep 18, 2025
Copy link
Member

@sairon sairon left a comment

Choose a reason for hiding this comment

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

LGTM with minor remark, but maybe it's not necessary to delve into the details.

@@ -0,0 +1,36 @@
---
title: "Home Assistant Core version"
Copy link
Contributor

Choose a reason for hiding this comment

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

Home Assistant Core version is a very generic title. Can we add the symptom in the title? Or is there a reason to just mention that it's something about the Core version?

This page seems like a troubleshooter to me.
We could use the Symptom, Description (or Cause), Resolution structure here.

Copy link
Member Author

Choose a reason for hiding this comment

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

These more-info unsupported come all in the same format, e.g.

https://www.home-assistant.io/more-info/unsupported/network_manager
https://www.home-assistant.io/more-info/unsupported/os_version

In a way the breadcrums above say that its about unsupported, but maybe that is not really clear enough. I think if we want to change then we should all at once, e.g. prefix with Unsupported: ... Or Unsupported - ...

Copy link
Contributor

@c0ffeeca7 c0ffeeca7 left a comment

Choose a reason for hiding this comment

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

tweaks

@home-assistant home-assistant bot marked this pull request as draft September 23, 2025 08:32
@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@agners agners requested a review from c0ffeeca7 September 23, 2025 13:33
@agners agners marked this pull request as ready for review September 23, 2025 13:33
Copy link
Contributor

@c0ffeeca7 c0ffeeca7 left a comment

Choose a reason for hiding this comment

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

Thank you, @agners and @sairon 👍

@c0ffeeca7 c0ffeeca7 merged commit fa294d4 into current Sep 23, 2025
9 checks passed
@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 labels Sep 23, 2025
@c0ffeeca7 c0ffeeca7 deleted the add-unsupported-reason-home-assistant-code-version branch September 23, 2025 13:36
@github-actions github-actions bot locked and limited conversation to collaborators Sep 24, 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 another repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants