You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
This is not how it works in hacs. You need to put this version-bump into or before the release-commit or it is ignored by hacs.
We had this problem in the past.
Hacs now sees the new release again as available for 2024.7.x
Hope no one tries to install it on 2024.9.x
The reason will be displayed to describe this comment to others. Learn more.
No sorry, but indeed it is not! HACS pulls your releasetag and nothing more. In that releasecommit it finds that it's 2024.7.0 requiered. HACS don't sees things/commits you do after a release.
2b0fd08
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not how it works in hacs. You need to put this version-bump into or before the release-commit or it is ignored by hacs.
We had this problem in the past.
Hacs now sees the new release again as available for 2024.7.x
Hope no one tries to install it on 2024.9.x
2b0fd08
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tackin
What do you mean precisely?
This change is now part of the v1.10.5 release package/tag. I thought this was correct.
2b0fd08
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.