Please Note required Database Updates in the changelog!

I agree with this request. I'm happy at least the minor version was updated with this release from .0 to .1 which may indicate some more changes than just bugfixes.
It would be ideal if each update is enhanced with a table indicating hierarchy version dependencies, with other installations on other machines running older versions. Like compatability with other RDM installations on other machines (do I need to upgrade all my clients connecting to a data store), RDM jump installations (do they need updates, which minimal version is required), and more.
Something that would give us enough information which minimal version is required on all other installation locations, and maybe an indication how to upgrade (for instance : consoles first, then data store, then jump servers, etc).

Our golden rule is we only allow database upgrades with major versions (13.0, 14.0, 15.0, ...) and in this case it is identified as such. In almost all cases (with the exception of MySQL going from v13 to v14) the database upgrade scripts are backwards compatible. That is you can run v13 & v14 side by side for some time. Keep in mind if you start doing new things in v14 (new sessions for example) that it will cause issues for people running v13 but simply installing v14 and using the system as usual won't cause issues.

There is one exception to the database upgrade rule. "Allow beta database upgrade" is checked in the data source configuration. We can maybe add a warning and identity that a database upgrade is required when we detect the option. Also, I would strongly suggest you not run with this option checked on a production environment. We use the beta scripts to prepare for the next major release.

You can also block users from installing newer versions of RDM using the version management option.

https://help.remotedesktopmanager.com/index.html?datasourcesettings_versionmanagement.htm