Make for dev and betas

[Limych]

Is it possible to make a library for the dev version of HA, or at least for the beta versions?

Today we miraculously caught an incompatibility with the new beta. If it hadn't been fixed, many users would have suffered.

[MatthewFlamm]

I try to release a version for every beta version. These are the most useful IMO. I will be releasing one soon.

This package used to track the dev versions, but this didn't work because homeassistant doesn't publish dev versions to PyPI.

#59 is intended to address this. Then users who want ultimate flexibility will have it. The big downside is that any change in homeassistant/core that requires changes here will break your testing. There is no 100% good solution I think.

[MatthewFlamm]

Clarification: I try to release one version for every set of beta versions, e.g. 2021.6.0.b*

[rautesamtr]

It's to bad that there's no better solution. The current approach makes it hard to implement changes once they are posted as dev blog articles. e.g. https://developers.home-assistant.io/blog/2022/12/01/entity_translations is from 1. december, so about 3 weeks old, but i still can't use translation_key since it breaks tests.

[MatthewFlamm]

I'm open to suggestions, but it is a hard problem, especially since the upstream package is not maintained for this use. There are small little breakages between versions that make this package neither forward or backwards compatible based on homeassistant versions. Supporting only released versions including betas at least makes it tractable. A CLI interface as in #59 would enable devs to throw caution to the wind and attempt against the dev branch anyway.