mirror of https://github.com/home-assistant/supervisor.git synced 2026-04-02 08:12:47 +01:00

Go to file

Stefan Agner 31c2fcf377 Treat empty string password as None in backup restore (#6618 )

* Treat empty string password as None in backup restore

Work around a securetar 2026.2.0 bug where an empty string password
sets encrypted=True but fails to derive a key, leading to an
AttributeError on restore. This also restores consistency with backup
creation which uses a truthiness check to skip encryption for empty
passwords.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Explicitly mention that "" is treated as no password

* Add tests for empty string password handling in backups

Verify that empty string password is treated as no password on both
backup creation (not marked as protected) and restore (normalized to
None in set_password).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Improve comment

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-10 09:53:43 +01:00

.devcontainer

Update Python to 3.13 (#5564 )

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

.github

Bump sigstore/cosign-installer from 4.0.0 to 4.1.0 (#6619 )

2026-03-10 08:30:46 +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

script

Add mypy to ci and precommit (#5969 )

2025-06-24 11:48:03 +02:00

supervisor

Treat empty string password as None in backup restore (#6618 )

2026-03-10 09:53:43 +01:00

tests

Treat empty string password as None in backup restore (#6618 )

2026-03-10 09:53:43 +01:00

wheels

Use unpublished local wheels during PR builds (#6374 )

2025-12-02 14:08:07 +01:00

.dockerignore

Use unpublished local wheels during PR builds (#6374 )

2025-12-02 14:08:07 +01:00

.gitignore

Use unpublished local wheels during PR builds (#6374 )

2025-12-02 14:08:07 +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

Bump ruff from 0.14.2 to 0.14.3 (#6280 )

2025-10-31 11:42:39 -04:00

.vcnignore

Sign code folder (#2725 )

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

AGENTS.md

Add AGENTS.md symlink (#6237 )

2025-10-08 10:44:49 +02:00

build.yaml

Use Python 3.14(.3) in CI and base image (#6586 )

2026-03-05 21:11:25 +01:00

CLAUDE.md

Add GitHub Copilot/Claude instruction (#5986 )

2025-07-04 07:05:05 +02:00

codecov.yaml

Remove annotations (#2007 )

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

Dockerfile

Remove cosign from container (#6442 )

2025-12-20 08:56:36 -05: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

Use Python 3.14(.3) in CI and base image (#6586 )

2026-03-05 21:11:25 +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.15.4 to 0.15.5 (#6616 )

2026-03-06 09:51:20 +01:00

requirements.txt

Bump setuptools from 82.0.0 to 82.0.1 (#6620 )

2026-03-10 07:28:04 +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.