Skip to content

Archive google-ai-haystack, google-vertex-haystack. Point to google-genai-haystack. #2348

Description

@julian-risch

We want users to use google-genai-haystack instead of google-ai-haystack and google-vertex-haystack. If we don't expect any future releases for the two older integrations, we should do the following:

  1. Update README files of the by adding a deprecation note and point to google-genai-haystack.
  2. Make a final release of the two integrations, for example the version can be x.y.z.post0 similar to the final Haystack 1.26.4.post0 release.
  3. Mark the two integrations on pypi as archived.

In the end, the README pages on pypi should look similar to the following, with a reference to google-genai-haystack.

Image

Activity

  1. changed the title [-]Mark google-ai-haystack and google-vertex-haystack as archived. Point to google-genai-haystack instead.[/-] [+]Mark `google-ai-haystack` and `google-vertex-haystack` as archived. Point to `google-genai-haystack` instead.[/+] on Sep 29, 2025
  2. changed the title [-]Mark `google-ai-haystack` and `google-vertex-haystack` as archived. Point to `google-genai-haystack` instead.[/-] [+]Archive `google-ai-haystack`, `google-vertex-haystack`. Point to `google-genai-haystack`.[/+] on Sep 29, 2025
  3. added and removed on Nov 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions