Darkdragon14/VolumeVault v1.12.0 on GitHub

Summary

Backup jobs can now define custom archive filename templates using tokens such as {name}, {source}, {id}, {year}, {month}, {day}, and {time}.
Existing backup jobs keep the previous volumevault-source-run-id archive naming until a template is configured.
The backup job form now previews generated archive names and warns when a template may overwrite earlier archives.
Russian interface translations received additional wording fixes for better consistency and readability. Thanks to @artyomboyko for the translation contribution.

This release includes a database migration adding backup_filename_template to backup jobs. Run the normal Laravel migrations during deployment.
No new environment variables or required manual configuration changes are needed.
Existing backup jobs keep their current archive naming unless you explicitly configure an archive name template.

Local verification before release included docker run --rm -v "/home/darkdragon/VolumeVault:/app" -w /app volumevault:local php artisan changelog:validate v1.12.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 tests/Feature/ChangelogTest.php.
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.