mirror of https://github.com/home-assistant/supervisor.git synced 2026-05-08 17:08:36 +01:00

T

Stefan Agner 8030b346e0 Load resolution evaluation, check and fixups early (#5696 )

* Load resolution evaluation, check and fixups early

Before #5652, these modules were loaded in the constructor, hence early
in `initialize_coresys()`. Moving them late actually exposed an issue
where NetworkManager connectivity setter couldn't get the
`connectivity_check` evaluation, leading to an exception early in
bootstrap.

Technically, it might be safe to load the resolution modules only in
`Core.connect()`, however then we'd have to load them separately for
pytest. Let's go conservative and load them the same place where they
got loaded before #5652.

* Load resolution modules in a single executor call

* Fix pytest

2025-02-28 16:59:22 +01:00

.devcontainer

Update Python to 3.13 (#5564 )

2025-01-21 11:57:30 +01:00

.github

Avoid space in update link of frontend update PR (#5694 )

2025-02-28 13:13:11 +01:00

.vscode

Migrate to Ruff for lint and format (#4852 )

2024-02-05 11:37:39 -05:00

rootfs/etc

Avoid empty newlines in Supervisor logs (#4698 )

2023-11-13 20:12:17 +01:00

supervisor

Load resolution evaluation, check and fixups early (#5696 )

2025-02-28 16:59:22 +01:00

tests

Load resolution evaluation, check and fixups early (#5696 )

2025-02-28 16:59:22 +01:00

.dockerignore

Add Audio layer / PulseAudio (#1523 )

2020-02-25 18:37:06 +01:00

.gitignore

Add mypy cache files to .gitignore (#1737 )

2020-05-21 12:07:20 +02:00

.ha-frontend-version

Autoupdate frontend to version 20250221.0 (#5616 )

2025-02-22 21:44:20 +01:00

.hadolint.yaml

Revert "Revert "Update base images to 3.11-alpine3.18 (#4639 )" (#4646 )" (#4657 )

2023-11-02 11:29:15 +01:00

.pre-commit-config.yaml

Update Python to 3.13 (#5564 )

2025-01-21 11:57:30 +01:00

.vcnignore

Sign code folder (#2725 )

2021-03-16 15:47:40 +01:00

build.yaml

Update Python to 3.13 (#5564 )

2025-01-21 11:57:30 +01:00

codecov.yaml

Remove annotations (#2007 )

2020-09-03 16:36:09 +02:00

Dockerfile

Define CPU architecture to fix armhf builds (#5670 )

2025-02-25 11:36:35 +01:00

LICENSE

Update LICENSE

2020-07-29 14:45:37 +02:00

MANIFEST.in

Add Audio layer / PulseAudio (#1523 )

2020-02-25 18:37:06 +01:00

pyproject.toml

Update Python to 3.13 (#5564 )

2025-01-21 11:57:30 +01:00

README.md

Add OHF logo to README (#5316 )

2024-09-30 18:42:08 +02:00

requirements_tests.txt

Bump ruff from 0.9.7 to 0.9.8 (#5689 )

2025-02-28 09:33:00 +01:00

requirements.txt

Bump setuptools from 75.8.1 to 75.8.2 (#5679 )

2025-02-27 09:04:03 +01:00

setup.py

Use version which is treated CalVer by AwesomeVersion (#5572 )

2025-01-24 09:59:50 +01:00

tox.ini

Migrate to Ruff for lint and format (#4852 )

2024-02-05 11:37:39 -05:00

README.md

Home Assistant Supervisor

First private cloud solution for home automation

Home Assistant (former Hass.io) is a container-based system for managing your Home Assistant Core installation and related applications. The system is controlled via Home Assistant which communicates with the Supervisor. The Supervisor provides an API to manage the installation. This includes changing network settings or installing and updating software.

Installation

Installation instructions can be found at https://home-assistant.io/getting-started.

Development

For small changes and bugfixes you can just follow this, but for significant changes open a RFC first. Development instructions can be found here.

Release

Releases are done in 3 stages (channels) with this structure:

Pull requests are merged to the main branch.
A new build is pushed to the dev stage.
Releases are published.
A new build is pushed to the beta stage.
The stable.json file is updated.
The build that was pushed to beta will now be pushed to stable.