LLMEOL CodeAP Studio

Gemini 1.0 Pro & PaLM 2 Bison Deprecation, Shutdown Dates & Migration Guide

Runs locally in your browser — 0 bytes uploaded Synced 2026-11-12 UTC · 5 variants · 1 ecosystems

Track confirmed UTC deprecation and shutdown dates for Gemini 1.0 Pro & PaLM 2 Bison (Google) across Google Vertex AI. Preview gemini-1.0-pro-002 → gemini-2.5-flash upgrades locally below, audit full configs in the Model Config Auditor, or benchmark token pricing in DevToken.

Tracked Variants 5
Earliest Upcoming EOL 2025-04-21
Recommended Upgrade gemini-2.5-flash
Ecosystems Covered Google Vertex AI

1. Quick .env & SDK Snippet Replacement Matcher

Edit or paste your .env assignment, LiteLLM route, or SDK model identifier below to check live 3-state EOL status and copy a ready-to-apply replacement diff locally in your browser.

2 of 2 configured models need migration
Full .env Auditor → Compare gemini-2.5-flash Cost in DevToken →

Replacement Diff Preview (gemini-1.0-pro-002 → gemini-2.5-flash)

# VERTEX_MODEL: gemini-1.0-pro-002 -> gemini-2.5-flash [RETIRED · EOL 2025-04-21]
- VERTEX_MODEL="gemini-1.0-pro-002"
+ VERTEX_MODEL="gemini-2.5-flash"

# model: gemini-1.0-pro-002 -> gemini-2.5-flash [RETIRED · EOL 2025-04-21]
- model: vertex_ai/gemini-1.0-pro-002
+ model: vertex_ai/gemini-2.5-flash

2. Cross-Ecosystem Gemini 1.0 Pro & PaLM 2 Bison Lifecycle Matrix (5)

Direct vendor APIs and cloud platforms retire dated snapshots on independent schedules. Verify the exact model ID, vendor lifecycle stage, and UTC shutdown date matching your deployment.

Gemini 1.0 Pro & PaLM 2 Bison lifecycle status, UTC shutdown dates, and replacement models across Google Vertex AI
Model ID Provider Calculated Status Confirmed Shutdown (UTC) Vendor Lifecycle Replacement & Migration Source
chat-bison Google Vertex AIGemini Models RETIRED 2025-04-21570d ago Retired
gemini-2.5-flash-lite Cost → Audit →
Docs ↗
gemini-1.0-pro-001 Google Vertex AIGemini Models RETIRED 2025-04-21570d ago Retired
gemini-2.5-flash Cost → Audit →
Docs ↗
gemini-1.0-pro-002 Google Vertex AIGemini Models RETIRED 2025-04-21570d ago Retired
gemini-2.5-flash Cost → Audit →
Docs ↗
gemini-1.0-pro-vision-001 Google Vertex AIGemini Models RETIRED 2025-04-21570d ago Retired
gemini-2.5-flash Cost → Audit →
Docs ↗
text-bison Google Vertex AIGemini Models RETIRED 2025-04-21570d ago Retired
gemini-2.5-flash-lite Cost → Audit →
Docs ↗

3. Production Migration Checklist (gemini-1.0-pro-002 → gemini-2.5-flash)

Follow this deterministic engineering sequence before retiring pinned snapshots in production services and SDK clients:

  1. Inventory pinned model IDs: Search repositories and deployment manifests for VERTEX_MODEL, vertex_ai/ LiteLLM routes, and dated snapshot strings in the Gemini 1.0 Pro & PaLM 2 Bison family (0 deprecated, 5 retired, 0 active variants tracked).
  2. Benchmark successor quality & token pricing: Validate structured output schemas, tool-calling payloads, and latency against gemini-2.5-flash, then compare input, output, and cached token rates in DevToken.
  3. Enforce keyless CI guardrails: Wire RSS, Atom, iCal feeds & CI Guard into pull-request checks so retired or deprecated Gemini 1.0 Pro & PaLM 2 Bison identifiers cannot re-enter production.

Compare sibling model families or inspect full provider-level schedules across every ecosystem hosting this family:

5. Gemini 1.0 Pro & PaLM 2 Bison Deprecation & Upgrade FAQ

Is Gemini 1.0 Pro & PaLM 2 Bison deprecated or retired across Google Vertex AI?

LLMEOL tracks 5 Gemini 1.0 Pro & PaLM 2 Bison variants across Google Vertex AI: 0 deprecated with scheduled shutdowns, 5 retired past their UTC EOL date, and 0 active with no announced shutdown date. Check the cross-ecosystem matrix above for exact snapshot dates.

What is the recommended replacement model when migrating off gemini-1.0-pro-002?

The primary recommended upgrade target for gemini-1.0-pro-002 is gemini-2.5-flash. Always test prompt formatting, max output tokens, and tool schemas on gemini-2.5-flash, and compare token pricing in DevToken before switching production traffic.

How can I replace gemini-1.0-pro-002 in .env and LiteLLM configs safely?

Paste your VERTEX_MODEL assignment or LiteLLM model block into the Quick Replacement Matcher on this page to generate an exact diff, or open the full Local Model Config Auditor to scan multi-service manifests with zero network upload.