Stable release with security coverage

I concur!

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 :)

We just released 1.2.0-rc1 and removed the LiteLLM dependency. Should we just go for 1.2.0 before ai releases a new version?

Should we just go for 1.2.0

Does that mean that there wouldn't be a stable ecosystem until ai releases 1.2.0 (possibly October)?

@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.

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.

We've opted into Security Coverage, and I've pushed up a stable 1.0.0.

I'm in touch with the maintainer of ai_vdb_provider_postgres to push forward with getting a stable release for that for 1.1.x / 1.2.x.

I think we can also push up a stable 1.1.x too.

Nice progress, thanks @ dan2k3k4! I completely agree with @jan.mashat in terms of scope.

Ported the VDB provider code into the amazee.ai provider module.

Released these fully stable versions for these providers/recipe:

• ai_provider_amazeeio versions 1.0.1 and 1.1.1
• ai_provider_litellm versions 1.0.0 and 1.1.0
• ai_provider_amazeeio_recipe versions 1.0.2 and 1.1.0

Marking this as fixed now.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.