Closed tjorim closed 7 months ago
@Sian-Lee-SA I also recommend pulling the 1.3.2 release from GitHub as it will still show up for people on older HA versions (if they enabled beta updated for this custom integration in HACS). See #186, #187 and #188.
Thanks for your input but will only do releases for Release Candidate when it comes to HACSand Home Assistant, theres a few reasons for this but primarily because Alpha/Beta releases can go through drastic changes from version to version which can be a development nightmare for integrations trying to keep up. eg. It could work in b0 then bot in b1 and need changing again etc.
Those who also use Beta are generally "testers" and for development, it would make sense to develop with the beta instead of acting like it's a release for a beta in prep for a RC. It was also my fault for jumping the gun here aswell as I honestly thought there was a 2023.12 RC out when I made the commit and release. This then led to confusion with those who are still on 2023.11 and those on beta 2023.12. As manual is also the other method for installing and one that I would've expected testers and developers using beta would use, then HACS would be more directed at those using non beta.
I don't think it's out of scope to assume the ones running beta are fine with the manual install till a RC is released. In fact I had a person raise an issue because they're installing manually but didn't read the release notes properly and wouldn't work on their 2023.11 installation.
So in future I'm going to be more careful about this integrations releases and not release until it's officially an RC release by Home Assistant. If there are beta fixes then they can be committed and downloaded straight from source without a release for those running beta and testing Home Assistant.
Allow Home Assistant beta versions by appending b0. Without b0, only official releases will be allowed.
Check the docs at https://hacs.xyz/docs/publish/start#hacsjson.
Will also need a new GitHub release. Closed #192.