Should components explicitly depend on "homeassistant" component in manifest? | Home Assistant | Page 1

spiral scarab Apr 28, 2026, 3:50 PM

#

It seems that on Python 3.14.3 conversation can get initialised before homeassistant and this results in a hard failure
https://github.com/home-assistant/core/actions/runs/25057100718/job/73402201810?pr=162263

#

I am not sure what the proper fix is, maybe https://github.com/home-assistant/core/pull/169386?

#

or https://github.com/home-assistant/core/pull/169385

rancid compass Apr 28, 2026, 5:37 PM

#

spiral scarab or <https://github.com/home-assistant/core/pull/169385>

In my opinion we should fix it properly and not just for the tests. That will hide the issue in our CI and so the problem can still exists in production

spiral scarab Apr 28, 2026, 5:50 PM

#

rancid compass In my opinion we should fix it properly and not just for the tests. That will hi...

If "homeassistant" is always loaded first, then it can't exist in production

rancid compass Apr 28, 2026, 5:51 PM

#

I meant the PR where you just add the test fixture

spiral scarab Apr 28, 2026, 5:53 PM

#

Sorry I'm confused
I don't understand why the test fixture is bad

#

in production, "homeassistant" and "conversation" will always get pre-loaded before "mcp_server"

#

only in tests we need to ensure "homeassistant" is loaded before "conversation"

#Should components explicitly depend on "homeassistant" component in manifest?