v1.10.5

Changes and Fixes

It has been a while since the last release but I've made a few helpful changes.

• Resolved an issue where the progress bar of the toast would extend outside of the toast container.
• Resolved an issue where the Backup Task failure email would send you the entire error message - with a very long scroll!
• Significantly improved how database backups are managed, they should be much more reliable now.
• Various package and dependency updates from Laravel. Not on Laravel 12 yet due to a couple of packages lacking support.

As a reminder, we strive to be on the latest stable PHP version as a minimum - PHP 8.2 is required to install Vanguard.

v1.10.4

Changes and Fixes

We had an issue with pushing to main but this has been resolved.

• Updated dependencies to address a security issue within Carbon.
• Added a link to the latest release patch notes in the footer.
• Made searching for Backup Tasks more reliable in the UI when using postgres databases.

v1.10.2

First release of the new year!

Changes and Fixes

• Updated dependencies of composer and npm.
• Improved the styling of connection information when you have an account connected to Vanguard.
• Included tips to help get your server connected should a connection fail when linking your remote server.
• Improved the design of the user dropdown to make it more consistent with the rest of the application.
• Added the start year to the copyright in the footer.

v1.10.1

Changes and Fixes

• Resolved an issue causing errors in scheduled commands due to unnecessary parameters.

v1.10.0

A couple of goodies in this release!

Changes and Fixes

• New Feature: You can now pin your favourite Backup Tasks for easy access.
• New Feature: Sentry support has been added for production environments.
• New Feature: A notice will now appear when creating a new Backup Destination, informing you that the values are securely encrypted.
• New Feature: A dark theme has been added to the admin instance dashboard.
• Improvement: Notices throughout the application now correctly display their background colour.
• Improvement: Ensured icon consistency when in mobile view.
• Improvement: Added a slight background to the avatar section on the 'My Profile' page.
• Improvement: Improved Danish translation coverage across the application.
• Fix: Fixed deprecation error notice when missing admin email addresses in the .ENV configuration.
• Fix: Fixed excessive whitespace when viewing the statistics page.
• Fix: Fixed failing tests when greeting falls on a holiday in certain circumstances.

If there are any problems with this release, please make an Issue and they'll be looked into.

Thanks!

v1.9.0

Changes

• Fixed an issue where the incorrect date would display on the profile settings page.
• Added more translation strings for the 'Danish' language.
• Fixed a bug where you would receive an error message when visiting the session management page with a language other than English set.
• Dependency updates.

If there are any translations missing, please let me know.

v1.8.5

Changes

• Updated dependencies to resolve security vulnerability within Laravel Pulse.

v1.8.4

Changes

• Feature: Added a Year in Review system to showcase backup statistics for the year period. This system is only active in the month of December and can be enabled/disabled regardless by setting the ENV variable YEAR_IN_REVIEWto true or false.

To visit your Year in Review, a new menu item should appear in your account settings list on the left-hand side called "Year in Review".

• Additional minor tweaks to PHPStan.

v1.8.3

Changes

• Updated depedencies to address a vulnerability found within the league/commonwork package.
• Laravel version used is now 11.34.2.

v1.8.2

Very few changes with this patch update but it primarily updates dependencies for the application. I do have plans for v1.8.3 soon in the next week once work settles down, this will be aiming to address static analysis errors after an update + a minor redirect glitch that happens sometimes.

Changes

• Updated dependencies to address a Laravel vulnerability. Details.

As always, I welcome suggestions on how to improve the application further, I'm pretty happy in the state it is in and it works brilliantly for my use case.