Skip to content

genblaze-google: VeoProvider docs/quickstart reference delisted veo-2.0/veo-3.0 slugs (same class as #233) #294

Description

@ffumero2003

Problem

libs/connectors/google/README.md and VeoProvider's docstring present veo-2.0-generate-001 / veo-3.0-generate-001 / veo-3.0-fast-generate-001 as the current models. None of them exist on the Gemini Developer API any more.

The README quickstart is copy-pasteable and broken:

# libs/connectors/google/README.md:46
.step(VeoProvider(), model="veo-3.0-generate-001", ...)

This is the same failure mode as #233 (delisted imagen-3.0-* slugs in the quickstart) — a new user follows the documented example and gets a preflight failure on their first run.

Evidence

Querying GET /v1beta/models with a working Gemini API key returns 54 models. The only Veo entries are:

veo-3.1-generate-preview
veo-3.1-fast-generate-preview
veo-3.1-lite-generate-preview

validate_model() — using the fallback_probe added in #248 — grades all three documented slugs as dead, and all three live ones as authoritative:

veo-3.0-fast-generate-001        not_found          probe   upstream probe returned DEAD
veo-3.0-generate-001             not_found          probe   upstream probe returned DEAD
veo-2.0-generate-001             not_found          probe   upstream probe returned DEAD

veo-3.1-lite-generate-preview    ok_authoritative   probe
veo-3.1-fast-generate-preview    ok_authoritative   probe
veo-3.1-generate-preview         ok_authoritative   probe

Locations

File Line What
libs/connectors/google/README.md 22 provider table lists all three delisted slugs
libs/connectors/google/README.md 46 quickstart example users copy
libs/connectors/google/genblaze_google/provider.py 52-54 docstring "Current GA examples"
libs/connectors/google/genblaze_google/_families.py 120, 145-146 example_slugs on the Veo families

(veo-3.0-generate-001 also appears in lmnt / luma / stability-audio test_catalog_decoupling.py as a deliberate foreign-slug fixture — those are fine and should not change.)

Suggested fix

Update the four locations above to the veo-3.1-*-preview slugs, and add a regression test mirroring the one #233 shipped (test_readme_imagen_quickstart_uses_live_slug / test_example_script_imagen_step_uses_live_slug) so the README quickstart slug is asserted against the catalog and can't silently rot again.

Worth noting these are -preview rather than GA, so the wording should probably say "current" rather than "GA".

Found via

Live verification while merging #286/#289 — the fallback_probe from #248 is what surfaced it.

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1bugSomething isn't workingdocumentationImprovements or additions to documentationproviders

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions