diff --git a/.idea/changes.md b/.idea/changes.md index 34179d9..76d2038 100644 --- a/.idea/changes.md +++ b/.idea/changes.md @@ -23,6 +23,7 @@ - Kept the no-restart behavior for blueprints, because blueprint deployment does not normally require a Home Assistant restart. - Restored blueprint backup/restore availability in the UI and backend: the restore button is visible again for blueprint installs, blueprint backups can be listed, and blueprint content can now be restored from backup without forcing a restart. - Fixed category-specific uninstall and restore messaging in the active panel: blueprints now reference `/config/blueprints` and explicitly state that no restart is required, while integrations keep the `/config/custom_components` restart warning. +- Updated the public documentation set (`README.md`, `README_DEVELOPER.md`, `README_FULL.md`, and `CHANGELOG.md`) for the completed blueprint backup, restore, uninstall, and restart-behavior work, and bumped the integration version to `0.7.6` for the next release. ### Documented - Captured the verified project identity from the repository and README files: Bahmcloud Store is a Home Assistant custom integration intended to behave like a provider-neutral store for custom integrations, similar to HACS but broader than GitHub-only workflows. diff --git a/CHANGELOG.md b/CHANGELOG.md index 4804a83..99e0507 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,20 @@ Sections: --- +## 0.7.6 - 2026-03-23 + +### Added +- Blueprint backup listing and restore support in the repository detail view. + +### Changed +- Install, update, uninstall, and restore feedback now reflects whether a restart is actually required for the selected content type. +- Blueprint restore dialogs and action messages now reference `/config/blueprints` instead of integration-only paths. + +### Fixed +- Blueprint updates now create usable content backups before overwriting files. +- Blueprint backups can be restored again from the active store UI after the previous restore-button regression. +- Blueprint uninstall confirmation text now matches the real uninstall behavior and no longer incorrectly warns about `/config/custom_components` or mandatory restarts. + ## 0.7.5 - 2026-03-23 ### Added diff --git a/README.md b/README.md index b1d956b..601cf8a 100644 --- a/README.md +++ b/README.md @@ -27,6 +27,7 @@ This README is for end users. - Pin repositories so important items stay easy to find - Use native Home Assistant update entities for installed integrations - Create and restore backups for integration installs and updates +- Create and restore blueprint content backups during blueprint updates and restore actions --- @@ -74,7 +75,7 @@ Installed to: - Expected repository content: `blueprints/...` - Install target: `/config/blueprints/...` -- Supports install and uninstall through the store +- Supports install, update, uninstall, backup, and restore through the store - No restart is normally required for blueprint deployment --- @@ -83,4 +84,3 @@ Installed to: - Developer documentation: `README_DEVELOPER.md` - Full user guide: `README_FULL.md` - diff --git a/README_DEVELOPER.md b/README_DEVELOPER.md index 44c6c65..5a8ee20 100644 --- a/README_DEVELOPER.md +++ b/README_DEVELOPER.md @@ -86,7 +86,8 @@ Category currently matters operationally: - Expected source layout: `blueprints/...` - Install target: `/config/blueprints/...` -- Initial support is focused on direct install and uninstall +- Supports install, update, uninstall, content backup, and content restore +- Restores and uninstalls are path-based and operate on the recorded installed blueprint files - Category-aware groundwork is in place so future content types can use their own install strategies ## HTTP API @@ -117,7 +118,7 @@ Base path: `/api/bcs` - README rendering - Release notes rendering - Version selection -- Backup restore UI for integrations +- Backup restore UI for integrations and blueprints ## Contributing to the Official Store Index @@ -156,4 +157,3 @@ The long-term architecture should remain category-aware: - category -> UI affordances This is especially important before Templates and Lovelace support are added, because those should stay compatible with established HACS expectations where possible. - diff --git a/README_FULL.md b/README_FULL.md index 2d2c92f..4572a10 100644 --- a/README_FULL.md +++ b/README_FULL.md @@ -58,7 +58,7 @@ That makes update checks more reliable when a repository uses tags or releases t - Source layout: `blueprints/...` - Install target: `/config/blueprints/...` -- Supports install and uninstall through the store +- Supports install, update, uninstall, backup, and restore through the store - Intended for blueprint repositories without integration-specific folder structures --- @@ -150,7 +150,8 @@ Blueprint installs normally do not require a Home Assistant restart. ### Blueprints -- Blueprint repositories can also be reinstalled from another selected version. +- Blueprint repositories can also be updated or reinstalled from another selected version. +- Blueprint updates create content backups before overwriting files. - The current blueprint path handling is focused on direct deployment to the blueprints folder. --- @@ -167,6 +168,7 @@ Blueprint installs normally do not require a Home Assistant restart. - Removes the installed blueprint files recorded by BCS - Cleans up empty directories below `/config/blueprints` when possible +- Does not require a restart under normal conditions --- @@ -198,6 +200,7 @@ Notes: ## Backups and Restore Integration installs and updates create backups before overwriting existing files. +Blueprint updates also create content backups before overwriting deployed blueprint files. Backup path: @@ -211,7 +214,16 @@ Restore flow: 4. Confirm restore 5. Restart Home Assistant if prompted -Restore is currently intended for integrations. +Restore is available for integrations and blueprints. + +Blueprint restore flow: + +1. Open the blueprint repository detail +2. Click **Restore** +3. Select a backup +4. Confirm restore + +Blueprint restores overwrite the recorded installed files under `/config/blueprints/...` and normally do not require a restart. --- @@ -273,7 +285,7 @@ Opening a repository detail view can force immediate enrichment for that reposit Restart usually matters only for integration changes. - Integration install/update/uninstall/restore: restart expected -- Blueprint install/uninstall: restart usually not needed +- Blueprint install/update/uninstall/restore: restart usually not needed BCS uses a Home Assistant repair flow to surface restart requirements for integration changes. diff --git a/custom_components/bahmcloud_store/manifest.json b/custom_components/bahmcloud_store/manifest.json index d9c6a44..5e88004 100644 --- a/custom_components/bahmcloud_store/manifest.json +++ b/custom_components/bahmcloud_store/manifest.json @@ -1,7 +1,7 @@ { "domain": "bahmcloud_store", "name": "Bahmcloud Store", - "version": "0.7.5", + "version": "0.7.6", "documentation": "https://git.bahmcloud.de/bahmcloud/bahmcloud_store", "config_flow": true, "platforms": ["update"],