v1.20.0

Summary

• VolumeVault can now connect to a Docker TCP endpoint, such as a socket proxy for the same Docker engine, through DOCKER_HOST. Docker CLI operations and temporary Offen backup containers use the configured endpoint, while the standalone TCP Compose configuration omits the unrestricted Unix socket mount. Remote Docker hosts remain unsupported, and TCP access must stay on a trusted private network.

Upgrade Notes

• No database migrations are included in this release.
• No environment changes are required for existing Unix-socket deployments. TCP proxy deployments use VOLUMEVAULT_DOCKER_HOST with the standalone docker-compose.tcp.yml file.
• Rebuild and restart the VolumeVault container after upgrading.

Verification

• Local verification before release included php artisan changelog:validate v1.20.0 --release --no-interaction.
• Local verification before release included php artisan test --compact (584 tests, 2,053 assertions).
• Local verification before release included npm run build.
• Local verification before release included vendor/bin/pint --dirty --format agent.