Summary
- Restore control over backup archive naming with an opt-in Use the exact template without a prefix checkbox and
use_exact_filenameAPI field. Existing jobs retain unique job/run prefixes by default; pre-restore safety backups always remain uniquely prefixed. - Show the complete filename preview, including the technical prefix, job timezone and UTF-8 length limits. Exact-name retention uses recorded destination/object identities and preserves unknown, ambiguous or changed archives. Historical checks support reordered JSON fields and large run histories.
- Update five Symfony components to 8.1.11 to address filesystem path, HTTP request/proxy handling, routing and YAML parser security advisories. Dependency audits reported no known vulnerabilities during validation; container images and running installations are not covered by these audits.
- Include updated API documentation and all nine UI/changelog languages.
Upgrade Notes
- Two database migrations add the exact-filename setting and archive-retention identity tracking. Back up the application database before upgrading. Once release images are published, pull the updated application and agent images and recreate containers, preserving storage volumes, configuration and
APP_KEY. Running installations are not updated automatically. - Update remote agents before enabling exact filenames. Agents also require the new capability when standard-mode retention shares a destination with exact-name history.
- Exact mode requires a nonempty filename template without an extension;
.tar.gzis appended automatically. Existing archives are not renamed. Exact names can overwrite archives from the same or another job sharing a destination, even with timestamp tokens. Use distinct templates or destinations. - Keep run history for exact-name retention. Unknown or unverifiable objects are preserved; metadata checks cannot detect every externally replaced same-name object. Pre-restore safety backups retain their unique prefix regardless of the setting.
- Reload the page to load the updated frontend assets.
Verification
- Feature validation passed the full PHP suite (1,974 passed, 34 optional/environment skips), frontend tests (271 passed), production build, Pint and diff checks. Twelve regression tests also passed against isolated MySQL 8.4. The existing frontend bundle-size warning remains.
- All three PR CI checks passed, including Laravel tests and MySQL/PostgreSQL migration recovery.
- Release preparation passed changelog tests (19 passed, 174 assertions), tagged-release changelog validation, frontend tests (271 passed), production build, Pint, Composer audit and diff checks.
- Container image publication is handled by the tag-triggered GitHub Actions workflow; no running installation is modified by this release.
Full Changelog: v2.0.9...v2.0.10