Enhancement request: ensure the Pi-Kit updater creates a backup before starting the download/install step. This avoids losing the previous working state if the download or staging fails mid-way.
Suggested behavior:
When apply/update is triggered, first create a backup of current web + api + version files (same as rollback uses), then proceed to download/stage/install the new release.
If download or verification fails, keep the backup intact and leave the system unchanged.
If install fails after staging, auto-rollback to that backup.
Context: Rollback sometimes fails in the UI; having the backup created before fetch/install reduces risk and makes recovery deterministic.
Enhancement request: ensure the Pi-Kit updater creates a backup *before* starting the download/install step. This avoids losing the previous working state if the download or staging fails mid-way.
Suggested behavior:
- When apply/update is triggered, first create a backup of current web + api + version files (same as rollback uses), then proceed to download/stage/install the new release.
- If download or verification fails, keep the backup intact and leave the system unchanged.
- If install fails after staging, auto-rollback to that backup.
Context: Rollback sometimes fails in the UI; having the backup created before fetch/install reduces risk and makes recovery deterministic.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Enhancement request: ensure the Pi-Kit updater creates a backup before starting the download/install step. This avoids losing the previous working state if the download or staging fails mid-way.
Suggested behavior:
Context: Rollback sometimes fails in the UI; having the backup created before fetch/install reduces risk and makes recovery deterministic.