VideoGenReview

What each AI video model's release notes say changed

Release notes from four model lines, dated

Four searches name makers outside the register, and each is read from the notes those makers or their platforms published: what changed, the day the note gives, and where a version question lands when no dated note exists. As of 2026-10-13.

Four makers, four kinds of recordOne maker keeps a changelog page, one an API update log beside an app release page, one two changelogs that date the same change on different days, and one is a platform whose announcements date another maker's versions. The register reads all four the same way: what changed, and the day the note gives.RunwayA changelog page withthirty-one dated notesA historyControls beforemodelsKling AIAn API update log thatopens withimage-to-videoA taskOne mode, then adefaultGoogle FlowTwo changelogs datingthe same change ondifferent daysTwo daysKept apart, notmergedHiggsfieldPlatform announcementsthat date anothermaker's versionsThe daysSomeone else'stimetableOne question: what changed, and on which dayWhat each maker's record turned out to be
Fig. 1 The records differ in shape; the question put to them does not.

Four vendors, four kinds of record. One reads Runway, whose changelog is the longest in this register and the closest thing to a diary a video maker keeps; one reads Kling AI, whose API update log begins with image-to-video; one reads Google Flow, where a version question has to be followed into two separate Google changelogs; and one reads Higgsfield, a platform whose own announcements are where another maker's versions get their days.

Each page works the same way. The register's entries for the line are set out in date order, so every statement carries the day the note gives rather than the day it was read. The maker's own pages are quoted beside them where the two describe the same thing, since a plan page and a changelog answer different questions. And one line in every table comes from SceneMixer, the pipeline this register follows, quoted from the sentence it was filed from.

Nothing here ranks the four, and none of the models was run. What is compared is what a dated record can settle — which version arrived, where, and on what day — against what a reader has to take from a maker's own description.

1In this column

  • Google Flow — why a version question about an image model lands on this register's edge, and what Google's two dated video lines show about how its changes get recorded.
  • Kling AI — what Kling's API update log says about image-to-video, note by note, and the frames and modes the later entries add.
  • Runway — one line's whole record read note by note, and what the register holds where a search asks about free access and unlimited allowances.
  • Seedance — two versions read from the days other platforms announced them, and the vendor's own undated listing rows that state length, resolution and references.

Dated: the maker pages behind these readings were checked on 2026-10-13, while the register's own entries were filed on 2026-09-25. How a note is read is set out on the method page, and every dated entry the register holds is on the full log.