Support

Hello,

thank you for the report, we forgot to add it. We're going to fix it ASAP

The changelog is generated automatically by the release script. I'm not sure why the .0 releases didn't get the changelog. I suspect something is up on the Mac I am using for releases so I switched to the backup Linux computer for the other releases.

Trying to update the changelog in releases already published requires database surgery which I'm really not willing to chance after having spent the last 7 weeks pulling 16 hour workdays to get these releases out of the door with more than decent Joomla 4 compatibility. If anything, once I get some sleep I'm going to see what is wrong with the Mac to make sure this doesn't repeat itself in the future.

If you really want to look at the changelog you can: a. download the extension ZIP and extract it.  Find the changelog.php file. It's the full changelog for the entire 5.x (Admin Tools) and 7.x (Akeeba Backup) release tree with a die() statement on top. Or b. install the software and click on the CHANGELOG button. These routes have always been available to you, at least since 2014 or thereabouts.

Most importantly, you don't really need to read the CHANGELOG but the Release Highlights at the top of the release notes. This is where I communicate everything you need to know about the new release. This has been true since circa 2013 when I realiszd that the changelog is not verbose enough to convey the background story behind a change, necessary actions or other nuanced information that are obvious to me as a developer but rather opaque to my users.

For Admin Tools 5.7 and Akeeba Backup 7.2 the only things you could only read in the Changelog is the exact changes I made to address Joomla 4 specific issues. Since you're on 3.9 they do not apply to you anyway. Here are the changelog excerpts you are missing.

Admin Tools 5.7.0
================================================================================
+ Improved Apache and IIS server signature removal
+ Improved CORS handling
+ Added support for Joomla 4 API application in the .htaccess Maker and Web.Config Maker
+ Added support for automatically serving .css.gz/.js.gz files in the .htaccess Maker and Web.Config Maker per Joomla 4 recommendations
- Removed Change Database Collation and Repair & Optimise Tables features under Joomla 4 (not supported by the J4 database driver)
- Removed the CSRFShield feature
~ Minimum requirements raised to PHP 7.1, Joomla 3.9
~ Use JAccess instead of DB queries [gh-223]
~ Improve the rendering of the System - Admin Tools plugin options
~ Improve the rendering of the component options
~ Changed the terms blacklist and whitelist to be more clear
~ Changed the term Security Exceptions to Blocked Requests for clarity
# [HIGH] Emergency Off-line completely broken under Joomla 4
# [HIGH] Purge Sessions does not work under Joomla 4
# [HIGH] Features with modal dialogs would not work under Joomla 4
# [MEDIUM] The "User groups to check for well-known passwords" feature could cause a PHP notice when modifying the component Options
# [MEDIUM] Temporary Super Users feature does not work when Monitor Super Users or Disable Editing Backend Users features are enabled
# [LOW] Some help text blocks were using the wrong class, making them illegible in Dark Mode.
# [LOW] Email Templates help text referenced country and continent which were removed in version 5.5.0.
# [LOW] Rescue URL doesn't work with Joomla 4
# [LOW] Notices thrown when plugin loaded in Joomla 4 Console application
# [LOW] Master Password page incorrectly referenced an UnlockIP view with an untranslated name; the correct is UnblockIP

Akeeba Backup 7.2.0
================================================================================
+ Restoration: Enable UTF8MB4 compatibility detection by default
~ Minimum requirements raised to PHP 7.1, Joomla 3.9
~ Using Joomla's cacert.pem instead of providing our own copy
~ Component Options page looks a bit nicer on Joomla 4
~ Joomla 4: fix profile selection drop-down display
# [HIGH] The restoration script can't read unquoted numeric values from the configuration.php file (used in Joomla 4)
# [HIGH] Joomla 4: Using the Smart Search filter during backup makes it impossible to use Smart Search on the restored site.
# [HIGH] Import from S3: infinite redirection loop
# [LOW] Very rare backup failures with a JS error
# [LOW] Unhandled exception page was incompatible with Joomla 4

Thank you, Frode! Have a good evening :)