v1.9.0

Summary

• Host path backup jobs can now stop selected containers before the backup and restart them afterwards, bringing host path backups in line with the existing Docker volume workflow.
• Selected containers are stored by name so they survive container recreation, and containers that are already stopped or no longer exist are skipped safely.
• VolumeVault now detects its own container and refuses to stop it during a backup, preventing a job from killing the process that is running it.
• Installations with unusual container setups can optionally override self-container autodetection with VOLUMEVAULT_CONTAINER_ID or VOLUMEVAULT_CONTAINER_NAME.

Upgrade Notes

• This release includes a database migration. Run your normal migration step, such as php artisan migrate --force, during deployment.
• No existing backup jobs require manual changes. The new container selection only applies when using host path backup sources with "stop containers before backup" enabled.
• VOLUMEVAULT_CONTAINER_ID and VOLUMEVAULT_CONTAINER_NAME are new optional environment variables. Most installations can leave them unset and rely on autodetection.

Verification

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