However, the confusing aspect is that your latest updates are not compatible with stable releases of Webmin and Usermin as one would expect them to be released in conjunction with one another.
This is understandable. I will improve this in the future to reduce confusion. Most of the time I try to avoid creating a dependency with unreleased version of Webmin/Usermin, unless necessary. What I will do in the future, I will document why exactly a dependency was created at the first place, to be clear.
For example, the dependencies is such are created when Webmin API receives a new subroutine that a new theme release relies on (major change, which will lead to a fatal breakage). Although, more often those dependencies are minor, and cannot be noticed in regular day use.
Is there any way of coordinating these releases to avoid this confusion?
Virtualmin repos receive Webmin updates with a certain delay for the particular reason.
Shall I upgrade or I’m fine?
I don’t remember making breaking changes this time. It shall work. However, for anyone reading it, I would suggest waiting for the official release of Webmin 1.980, which will ship the latest Authentic Theme 19.82. Nevertheless, if you feel comfortable rolling back the latest installed theme version using
theme-update.sh script (in case something goes wrong), then go ahead and give it a try. It won’t damage anything, even though some things may not work as designed.