●API — Gemini 3.5 Flash is generally available and now powers gemini-flash-latest for sustained agentic and coding performance●AGENT — Managed Agents enter public preview, running stateful autonomous agents in Google-hosted isolated Linux sandboxes●SEARCH — File Search adds multimodal search, embedding and searching images natively with gemini-embedding-2●RESEARCH — A new Deep Research agent adds collaborative planning, visualization, MCP server integration, and File Search●SHEETS — Gemini in Sheets analyzes surrounding data to diagnose and fix formula errors in one click●ROADMAP — Gemini 3.5 Pro slips to July for refinement; the Flash line leads for now●API — Gemini 3.5 Flash is generally available and now powers gemini-flash-latest for sustained agentic and coding performance●AGENT — Managed Agents enter public preview, running stateful autonomous agents in Google-hosted isolated Linux sandboxes●SEARCH — File Search adds multimodal search, embedding and searching images natively with gemini-embedding-2●RESEARCH — A new Deep Research agent adds collaborative planning, visualization, MCP server integration, and File Search●SHEETS — Gemini in Sheets analyzes surrounding data to diagnose and fix formula errors in one click●ROADMAP — Gemini 3.5 Pro slips to July for refinement; the Flash line leads for now

TAG

propertyOrdering

1 articles

← Back to all tags

Gemini API¹ Structured Output¹ Snapshot Testing¹ JSON Schema¹

◈ Gemini API/2026-06-27Advanced

Your Gemini Structured Output Keys Keep Reordering — Pin Them With propertyOrdering

You constrained the shape with responseSchema, yet the JSON key order shifts between calls and your snapshot tests go red for no reason. Here is why field order is not guaranteed by default, how propertyOrdering fixes it, how Pydantic sets it for you, and how to align few-shot examples — all with working code.