Currently the integration is maintained by releasing a new version (hacs commit id upgrade) when an new change is merged to the master branch.
The last change that was merged (for #36) contained a breaking change that required users to re-add the integration after upgrading.
It would be nice for end-users if the release notes were to inform them of the required action to get the integration working after upgrade.
So that end-users won't have to search / open issues in order to get everything working again.
Furthermore, this would also allow end users to better determine whether to upgrade at that time and what new features they could try out
Currently the integration is maintained by releasing a new version (hacs commit id upgrade) when an new change is merged to the master branch. The last change that was merged (for #36) contained a breaking change that required users to re-add the integration after upgrading. It would be nice for end-users if the release notes were to inform them of the required action to get the integration working after upgrade.
So that end-users won't have to search / open issues in order to get everything working again. Furthermore, this would also allow end users to better determine whether to upgrade at that time and what new features they could try out