Fix repair issue description format

The last sentence in the repair issue's description was added to the bullet of the last file. Fixed that.

Full Changelog: v1.12.1...v1.12.2

Fix `system_was_patched` repair ticket

All system_was_patched repair tickets used the same ID, so dismissing it once would cause it to not appear again. This is fixed now by deleting a previous ticket before creating a new one.

Full Changelog: v1.12.0...v1.12.1

Report base mismatch on integration setup

There is a 5 minutes delay (by default) from the integration setup until it applies the patches. Reporting a base file mismatch was also done only after the 5 minutes delay. With this release, base file mismatch is reported immediately on integration setup.

Full Changelog: v1.11.0...v1.12.0

Issue repair ticket after successful patch

A successful patch process includes a core restart, but users previously had little visibility into this flow, and relevant log entries disappeared during the restart. This release introduces a repair issue that lists all files patched, providing clearer insight into what was updated.

Full Changelog: v1.10.1...v1.11.0

Better error handling when fetching URLs

Regular file existence checks are part of the configuration validation logic.
However, URLs are only fetched during the actual patching process.
The following changes were implemented to improve error handling of URL download:

1. Downloading all URLs (of all patches) as the initial step of the patching process so we can stop on error before any patch was applied.
2. Raise an exception if the HTTP status code is not success.

Full Changelog: v1.10.0...v1.10.1

Make "name" parameter optional

The name parameter is now optional. When it exists, it will be appended to the rest of the parameters (like before). When it doesn't exist, the rest of the parameters should be provided as full path, including the file name.

Full Changelog: v1.9.0...v1.10.0

URL support

Add URL support for the base and patch parameters.

Full Changelog: v1.8.0...v1.9.0

Fix patch.reload when the config has secrets

The action patch.reload was failing when configuration.yaml includes secrets (in any section, not necessarily the patch section). It's fixed now.

Full Changelog: v1.7.0...v1.8.0

Wait for recorder migration

New logic to wait until the recorder migration process is done.

Additional details: Recorder migration is typically running when upgrading to a new major version of Home Assistant. The migration process can take a considerable amount of time. It's not possible to restart Home Assistant during the migration process (rightfully), which is required by the patching process. The solution is to wait for the recorder migration process to complete, and only then execute the patching process, including a restart when needed.

Full Changelog: v1.6.0...v1.7.0

Restart parameter

A new restart optional parameter. Default is true. When it's set to false, there is no HA restart after a patch.

Full Changelog: v1.5.1...v1.6.0