Correct. The next version will update both plugins' versions to be the same as the component and the package.
Some background. We use Phing to build all of our software, using the common Phing build script from Akeeba Build Files with customisations for each software we release. This allows us to have a standardised method for building software, creating releases, publishing update streams, upload development releases, create the symlinks we need for local development, convert our documentation from DocBook XML to PDF and so on and so forth.
Build Files has an xml-version task which automatically updates the version and build date in XML manifests. However, the Admin Tools repository wasn't calling it because of a customisation we had made in the build process: we have to create a slightly different plg_system_admintools plugin for Core and Pro versions. As a result the XML manifests of the other two plugins, plg_actionlog_admintools and plg_installer_admintools, were not being updated. I have added xml-version to the Admin Tools build customisation and now they are going to be updated when we release a new version.
Once again, thank you for bringing this to my attention!
Merry Christmas :)
Nicholas K. Dionysopoulos
Lead Developer and Director
π¬π·Greek: native π¬π§English: excellent π«π·French: basic β’ π My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!