When an update for an add-on such as NodeRED or Zwave JS UI is available, it’s hard to figure out what’s actually changed.
The release notes shown in Home Assistant only refer to changes made to the add-on package itself, not to the package’s dependencies. Crucially, it doesn’t link to the release notes for the core components of the add-on themselves (what the add-on actually wraps up for consumption).
So for example, if I want to know what’s new in the ZWave JS UI add-on, I have to scroll down its release notes to where it lists updated dependencies, then search github to locate the specified zwavejs2mqtt release and read its notes. And since zwavejs2mqtt rolls up zwavejs as a dependency too, I need to repeat the process to find those notes. It’s hard to discover new features or breaking changes this way.
Could we improve how add-ons are packaged for release such that the release notes embed or link to information about the most important encapsulated dependencies?