v1.14.0

Summary

• Restore workflows now support in-place and safe in-place restores for Docker volume backup jobs, including exact volume-name confirmation, optional safety backups before overwriting, automatic container stop/start handling for safe restores, improved backup filtering, and direct "Restore this backup" entry points from backup runs.
• Backup job pages now include a paginated Restore history tab alongside Run history, so restores are visible from the job they belong to with status, mode, source and target volumes, timing, and links to details.
• Backup and restore activity now records the initiating user where applicable, and restore start, success, and failure notifications can be sent through the job's existing notification channels with customizable restore message templates.

Upgrade Notes

• This release includes database migrations for restore metadata, initiator attribution, restore notification templates, and restore liveness tracking; run migrations as part of the upgrade.
• API clients can use the new inplace and safe_inplace restore modes on POST /api/v1/backup-jobs/{id}/restore; new_volume remains the safest mode and the only mode for host-path backup jobs.
• No new environment variables are required.
• Rebuild and restart the VolumeVault container after upgrading.

Verification

• Local verification before release included docker run --rm --user "$(id -u):$(id -g)" -v "/home/darkdragon/VolumeVault:/app" -w /app volumevault:local php artisan changelog:validate v1.14.0 --release --no-interaction.
• Local verification before release included docker run --rm --user "$(id -u):$(id -g)" -v "/home/darkdragon/VolumeVault:/app" -w /app volumevault:local php artisan test --compact.
• Local verification before release included docker run --rm --user "$(id -u):$(id -g)" -v "/home/darkdragon/VolumeVault:/app" -w /app volumevault:local php ./vendor/bin/pint --dirty --format agent.
• Local verification before release included npm run build.