The preview lines that have already gone

Two preview identifiers in this family carry a shutdown date that has already passed, and no entry in the register names them today. This is one of the retirements here that have already completed, and it shows what a finished one looks like from outside. From 1 source page, read 2026-09-22; no maker pays to be listed.

Inclusion rule. An entry appears when it names this line on a page a reader can reach without an account, or when it publishes a lifecycle date for it. Absence is recorded as a row. Order. The entry publishing the date first, then the applications as one row.

1A finished retirement leaves a dated row and nothing else

The identifiers are gone and the row is still there, which is the useful half. A reader can confirm that the line existed, that it had a date, and that the date has passed, all from one page.

Nothing else survives. No application names these strings, no successor is recorded beside them, and nothing says what happened to callers who had not moved. That is the ordinary aftermath rather than a failure of this maker's documentation.

2Preview lines carried the earlier date

These identifiers were retired before the released ones in the same generation, which matches the platform policies elsewhere in this register: a preview stage buys less notice. Here the stage is encoded in the identifier string rather than published as a state.

So a team that built during a preview period was on the shorter runway without any page grouping the two as one decision. The register records that as a naming convention doing a state system's work.

3Why a completed retirement belongs in a register of announcements

Most of this site records dates that have not arrived. Keeping one that has is what lets a reader calibrate the others: it shows the wording, the interval and the absence of a successor as they actually resolved.

Completed cases are few, and they are the only evidence available about how these endings finish. The consumer closure the calendar also records is one of them.

• veo-3.0-generate-preview and veo-3.0-fast-generate-preview
  12 November 2025shutdown dateGoogle, Gemini deprecations / recorded 2026-09-22
• What a date in that table commits to
  The shutdown dates listed indicate the earliest possible dates on which a model might be retiredGoogle, Gemini deprecations / recorded 2026-09-22
• How many days of advance notice
  No number of days published (as of 2026-09-12)promised but never countedGoogle, Gemini deprecations / recorded 2026-09-22

4When the model underneath changes

Model end dates touch “Veo 3 preview lines”; SceneMixer's guides describe how its pipeline treats the models it runs:

A script is read once per project; switching affects new tasks, such as regenerating a storyboard.

SceneMixer, Which text tier for reading and storyboards — “Do I need to re-read the script when I switch?” (read 2026-10-13)

Downloads and the asset library follow your Music switch; a shared link always plays the version with the episode’s music.

SceneMixer, Background Music in an AI Short Drama: The Built-in Score — “Does the music carry into downloads, the library and shared links?” (read 2026-10-13)

5Sources

Each row is read from the page that entry publishes itself, 2026-09-22, and any date comes from whoever makes the model. Every announced date is on the calendar. Other models read this way: Kling 3.0, Kling 2.5 Turbo.