The stable release
Google announced general availability of Gemini 2.5 Flash Image on October 2, 2025.
Promote a workflow, not just a model name
A preview evaluation often lives in a notebook or a one-off script. Before promoting it, capture the full contract: accepted source formats, prompt construction, output parsing, storage, and error handling. These application decisions need their own version history.
Keep the model ID in configuration rather than scattered through the codebase. A stable release is an opportunity to make that separation explicit, while preserving the requests that already worked during evaluation.
Use a small acceptance set
Select representative briefs from actual work: a product on a plain background, a composition with text, and an edit using a reference image. Review the new configuration against the saved candidates. Include failed or ambiguous briefs; only testing your best prompt hides the operational risk.
Roll out to a limited workload first. Track approved assets, failed requests, and time spent reviewing. General availability is a provider release status, not a guarantee about your own end-to-end workflow.
Maintain the record
Document why the application adopted this version and which acceptance checks were performed. That short record is useful when a future model offers a different balance of cost, speed, and quality.
Official sources
Provider announcements describe the underlying APIs. Check the live XMH.NET catalog for the models and request formats available to your account.