- Issue created by @christophweber
- 🇨🇭Switzerland schnitzel
yep, we're working on it, we're building upstream 1.1.0 support in #3529779 and then will release a stable of the provider as well :)
- 🇦🇹Austria pmelab
We just released
1.2.0-rc1and removed the LiteLLM dependency. Should we just go for1.2.0before ai releases a new version? - 🇭🇺Hungary jan.mashat
Should we just go for 1.2.0
Does that mean that there wouldn't be a stable ecosystem until
aireleases1.2.0(possibly October)? - 🇨🇭Switzerland dan2k3k4 Zurich
@jan.mashat I believe @pmelab meant: should we make "ai_provider_amazeeio" release a stable 1.2.0 as we're tied with the version of "ai" module. If the "ai" module releases 1.3.x branch, then we may likely have to bump up "ai_provider_amazeeio" too.
- 🇭🇺Hungary jan.mashat
My wish would be to have stable "ai_provider_amazeeio" releases shadowing stable "ai" versions.
Currently "ai" has the following stable versions: 1.0.6 and 1.1.1
Since this is a fast moving ecosystem, it probably doesn't make sense to put much effort into 1.0, but I would hope that a stable 1.1 release of "ai_provider_amazeeio" will arrive soon - and later on a stable 1.2 when "ai" comes out with that release.