docs: mark Runway Gen3a and legacy Kling models as EOL - #1326
Conversation
Retire deprecated Partner Node tutorials and workflows, add migration tables, and sync i18n hashes across EN/ZH/JA/KO.
|
Warning Review limit reached
Next review available in: 17 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Replace `<=` in prose with "must not exceed" so mint broken-links can parse the page.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
zh/tutorials/partner-nodes/runway/video-generation.mdx (1)
56-56: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winCorrect the workflow type.
This says “text-to-image,” but this page and its steps describe image-to-video.
Proposed fix
-你可参考图片中的序号来完成最基础的文生图工作流运行： +你可参考图片中的序号来完成最基础的图生视频工作流运行：🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@zh/tutorials/partner-nodes/runway/video-generation.mdx` at line 56, Update the workflow description near the referenced sentence to identify it as the basic image-to-video workflow instead of text-to-image, while preserving the existing instruction about following the numbered steps in the image.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@built-in-nodes/KlingStartEndFrameNode.mdx`:
- Line 12: Update the EOL notice in KlingStartEndFrameNode to include the legacy
model option “kling-v2-1” alongside “kling-v1-5” and “kling-v1-6,” while
preserving the existing September 15, 2026 retirement date and replacement
guidance.
In `@built-in-nodes/KlingVirtualTryOnNode.mdx`:
- Line 15: Update the displayed node name in the Kling Virtual Try On Node
documentation to “Kling Virtual Try-On Node,” preserving the rest of the
description unchanged.
In `@built-in-nodes/RunwayFirstLastFrameNode.mdx`:
- Line 12: Update the EOL notices at
built-in-nodes/RunwayFirstLastFrameNode.mdx:12-12 and
built-in-nodes/RunwayImageToVideoNodeGen3a.mdx:12-12 to state that Runway will
reach end of life on July 30, 2026. Update the corresponding Chinese notices at
zh/built-in-nodes/RunwayFirstLastFrameNode.mdx:12-12 and
zh/built-in-nodes/RunwayImageToVideoNodeGen3a.mdx:12-12 to use future-tense
wording, including “将于,” while preserving the retirement date and replacement
guidance.
In `@tutorials/partner-nodes/pricing.mdx`:
- Around line 817-825: Change the EOL warning and status for gen3a_turbo and the
Runway First-Last-Frame node to future tense, stating that retirement is
scheduled for July 30, 2026 rather than completed. Apply this in
tutorials/partner-nodes/pricing.mdx lines 817-825,
ja/tutorials/partner-nodes/pricing.mdx lines 859-867,
ko/tutorials/partner-nodes/pricing.mdx lines 856-864, and
zh/tutorials/partner-nodes/pricing.mdx lines 859-867, preserving the existing
active entries and dates.
- Line 486: Update the Legacy heading to replace the em dash after the version
list with a colon or separate sentence, while preserving the existing version
and EOL date information.
In `@tutorials/partner-nodes/runway/video-generation.mdx`:
- Around line 15-24: Update the Runway retirement notice and removed-template
sections so they do not state that the July 30, 2026 EOL and removals have
already occurred before that date; use future-tense wording while preserving the
listed replacements. Apply the same aligned changes in
tutorials/partner-nodes/runway/video-generation.mdx (15-24),
ja/tutorials/partner-nodes/runway/video-generation.mdx (18-27),
ko/tutorials/partner-nodes/runway/video-generation.mdx (18-27), and
zh/tutorials/partner-nodes/runway/video-generation.mdx (18-27), keeping each
translation accurate.
---
Outside diff comments:
In `@zh/tutorials/partner-nodes/runway/video-generation.mdx`:
- Line 56: Update the workflow description near the referenced sentence to
identify it as the basic image-to-video workflow instead of text-to-image, while
preserving the existing instruction about following the numbered steps in the
image.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: c6b0f83c-b6c7-4792-be6d-d3108c761bb6
📒 Files selected for processing (25)
built-in-nodes/KlingDualCharacterVideoEffectNode.mdxbuilt-in-nodes/KlingImage2VideoNode.mdxbuilt-in-nodes/KlingSingleImageVideoEffectNode.mdxbuilt-in-nodes/KlingStartEndFrameNode.mdxbuilt-in-nodes/KlingVirtualTryOnNode.mdxbuilt-in-nodes/RunwayFirstLastFrameNode.mdxbuilt-in-nodes/RunwayImageToVideoNodeGen3a.mdxja/tutorials/partner-nodes/kling/kling-3-0.mdxja/tutorials/partner-nodes/pricing.mdxja/tutorials/partner-nodes/runway/video-generation.mdxko/tutorials/partner-nodes/kling/kling-3-0.mdxko/tutorials/partner-nodes/pricing.mdxko/tutorials/partner-nodes/runway/video-generation.mdxsnippets/ja/tutorials/partner-nodes/supported-models.mdxsnippets/ko/tutorials/partner-nodes/supported-models.mdxsnippets/tutorials/partner-nodes/supported-models.mdxsnippets/zh/tutorials/partner-nodes/supported-models.mdxtutorials/partner-nodes/kling/kling-3-0.mdxtutorials/partner-nodes/pricing.mdxtutorials/partner-nodes/runway/video-generation.mdxzh/built-in-nodes/RunwayFirstLastFrameNode.mdxzh/built-in-nodes/RunwayImageToVideoNodeGen3a.mdxzh/tutorials/partner-nodes/kling/kling-3-0.mdxzh/tutorials/partner-nodes/pricing.mdxzh/tutorials/partner-nodes/runway/video-generation.mdx
| --- | ||
|
|
||
| <Warning> | ||
| **End of life (EOL)**: Legacy model options using `kling-v1-5` and `kling-v1-6` are scheduled for retirement on **September 15, 2026**. Use [`api_kling_v3_flf2v`](/tutorials/partner-nodes/kling/kling-3-0#legacy-kling-models-eol) or Kling O3 FLF2V instead. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Include kling-v2-1 in the EOL warning.
This page still exposes kling-v2-1 at Line 27, but the warning only names kling-v1-5 and kling-v1-6. Align the notice with the legacy-model retirement scope so users of kling-v2-1 also receive the September 15, 2026 warning.
🧰 Tools
🪛 GitHub Check: Mintlify Validation (dripart) - vale-spellcheck
[warning] 12-12: built-in-nodes/KlingStartEndFrameNode.mdx#L12
Did you really mean 'Kling'?
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@built-in-nodes/KlingStartEndFrameNode.mdx` at line 12, Update the EOL notice
in KlingStartEndFrameNode to include the legacy model option “kling-v2-1”
alongside “kling-v1-5” and “kling-v1-6,” while preserving the existing September
15, 2026 retirement date and replacement guidance.
| **End of life (EOL)**: The Kolors Virtual Try-On API (`kolors-virtual-try-on`, `kolors-virtual-try-on-v1-5`) is scheduled for retirement on **September 15, 2026**. Use [Flux Virtual Try-On](/built-in-nodes/FluxVTONode) instead. | ||
| </Warning> | ||
|
|
||
| Kling Virtual Try On Node. Input a human image and a cloth image to try on the cloth on the human. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Hyphenate “Try-On” in the node name.
Use “Kling Virtual Try-On Node” for consistent compound-noun styling.
🧰 Tools
🪛 GitHub Check: Mintlify Validation (dripart) - vale-spellcheck
[warning] 15-15: built-in-nodes/KlingVirtualTryOnNode.mdx#L15
Did you really mean 'Kling'?
🪛 LanguageTool
[grammar] ~15-~15: Use a hyphen to join words.
Context: ...) instead. Kling Virtual Try On Node. Input a human image and a cloth...
(QB_NEW_EN_HYPHEN)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@built-in-nodes/KlingVirtualTryOnNode.mdx` at line 15, Update the displayed
node name in the Kling Virtual Try On Node documentation to “Kling Virtual
Try-On Node,” preserving the rest of the description unchanged.
Source: Linters/SAST tools
| --- | ||
|
|
||
| <Warning> | ||
| **End of life (EOL)**: This node reached end of life on **July 30, 2026** when Runway retired Gen-3 Alpha Turbo. For first-last-frame video, use [Kling 3.0 FLF2V](/tutorials/partner-nodes/kling/kling-3-0) or other supported FLF2V templates. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Correct the premature EOL tense across all Runway pages. As of July 27, 2026, July 30, 2026 is still future; use future-tense wording until that date.
built-in-nodes/RunwayFirstLastFrameNode.mdx#L12-L12: change “reached end of life” to “will reach end of life on July 30, 2026.”built-in-nodes/RunwayImageToVideoNodeGen3a.mdx#L12-L12: use the same future-tense EOL wording.zh/built-in-nodes/RunwayFirstLastFrameNode.mdx#L12-L12: change “已于” to “将于.”zh/built-in-nodes/RunwayImageToVideoNodeGen3a.mdx#L12-L12: describe the July 30 retirement as future rather than completed.
🧰 Tools
🪛 GitHub Check: Mintlify Validation (dripart) - vale-spellcheck
[warning] 12-12: built-in-nodes/RunwayFirstLastFrameNode.mdx#L12
Did you really mean 'Kling'?
[warning] 12-12: zh/built-in-nodes/RunwayFirstLastFrameNode.mdx#L12
Did you really mean 'Kling'?
📍 Affects 4 files
built-in-nodes/RunwayFirstLastFrameNode.mdx#L12-L12(this comment)built-in-nodes/RunwayImageToVideoNodeGen3a.mdx#L12-L12zh/built-in-nodes/RunwayFirstLastFrameNode.mdx#L12-L12zh/built-in-nodes/RunwayImageToVideoNodeGen3a.mdx#L12-L12
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@built-in-nodes/RunwayFirstLastFrameNode.mdx` at line 12, Update the EOL
notices at built-in-nodes/RunwayFirstLastFrameNode.mdx:12-12 and
built-in-nodes/RunwayImageToVideoNodeGen3a.mdx:12-12 to state that Runway will
reach end of life on July 30, 2026. Update the corresponding Chinese notices at
zh/built-in-nodes/RunwayFirstLastFrameNode.mdx:12-12 and
zh/built-in-nodes/RunwayImageToVideoNodeGen3a.mdx:12-12 to use future-tense
wording, including “将于,” while preserving the retirement date and replacement
guidance.
| | motion control | — | pro | 23.63 | | ||
|
|
||
| #### Legacy (v2-5-turbo, v2-master, v1.x) | ||
| #### Legacy (v2-5-turbo, v2-master, v1.x) — EOL September 15, 2026 |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Replace the em dash in this heading.
Use a colon or a second sentence instead.
Proposed fix
-#### Legacy (v2-5-turbo, v2-master, v1.x) — EOL September 15, 2026
+#### Legacy (v2-5-turbo, v2-master, v1.x): EOL September 15, 2026As per coding guidelines, “In English documentation, avoid em dashes (—).”
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| #### Legacy (v2-5-turbo, v2-master, v1.x) — EOL September 15, 2026 | |
| #### Legacy (v2-5-turbo, v2-master, v1.x): EOL September 15, 2026 |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@tutorials/partner-nodes/pricing.mdx` at line 486, Update the Legacy heading
to replace the em dash after the version list with a colon or separate sentence,
while preserving the existing version and EOL date information.
Source: Coding guidelines
| <Warning> | ||
| **End of life (EOL)**: `gen3a_turbo` and the Runway First-Last-Frame node reached end of life on **July 30, 2026**. Use Gen4 Turbo for image-to-video instead. | ||
| </Warning> | ||
|
|
||
| | model | Credits | | ||
| | :---------- | :---------- | | ||
| | gen3a_turbo | 15.09 / sec | | ||
| | gen4_turbo | 15.09 / sec | | ||
| | aleph2 | 84.48 / sec | | ||
| | model | Credits | Status | | ||
| | :---------- | :---------- | :----- | | ||
| | gen4_turbo | 15.09 / sec | Active | | ||
| | gen3a_turbo | 15.09 / sec | EOL (July 30, 2026) | | ||
| | aleph2 | 84.48 / sec | Active | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Use future tense until July 30, 2026.
As of July 27, 2026, gen3a_turbo has not yet reached its July 30, 2026 EOL date. Marking it as already retired can prematurely steer users away from an active option.
tutorials/partner-nodes/pricing.mdx#L817-L825: change the warning and status from completed EOL to scheduled EOL.ja/tutorials/partner-nodes/pricing.mdx#L859-L867: update the warning and status to future tense.ko/tutorials/partner-nodes/pricing.mdx#L856-L864: update the warning and status to future tense.zh/tutorials/partner-nodes/pricing.mdx#L859-L867: update the warning and status to future tense.
🧰 Tools
🪛 GitHub Check: Mintlify Validation (dripart) - vale-spellcheck
[warning] 817-817: ja/tutorials/partner-nodes/pricing.mdx#L817
Did you really mean 'Recraft'?
[warning] 817-817: ja/tutorials/partner-nodes/pricing.mdx#L817
Did you really mean 'Vectorize'?
[warning] 817-817: ja/tutorials/partner-nodes/pricing.mdx#L817
Did you really mean 'Recraft'?
[warning] 818-818: ja/tutorials/partner-nodes/pricing.mdx#L818
Did you really mean 'Recraft'?
[warning] 819-819: ja/tutorials/partner-nodes/pricing.mdx#L819
Did you really mean 'Recraft'?
[warning] 821-821: ja/tutorials/partner-nodes/pricing.mdx#L821
Did you really mean 'Reve'?
[warning] 818-818: ko/tutorials/partner-nodes/pricing.mdx#L818
Did you really mean 'Reve'?
[warning] 817-817: zh/tutorials/partner-nodes/pricing.mdx#L817
Did you really mean 'Recraft'?
[warning] 817-817: zh/tutorials/partner-nodes/pricing.mdx#L817
Did you really mean 'Recraft'?
[warning] 818-818: zh/tutorials/partner-nodes/pricing.mdx#L818
Did you really mean 'Recraft'?
[warning] 819-819: zh/tutorials/partner-nodes/pricing.mdx#L819
Did you really mean 'Recraft'?
[warning] 821-821: zh/tutorials/partner-nodes/pricing.mdx#L821
Did you really mean 'Reve'?
📍 Affects 4 files
tutorials/partner-nodes/pricing.mdx#L817-L825(this comment)ja/tutorials/partner-nodes/pricing.mdx#L859-L867ko/tutorials/partner-nodes/pricing.mdx#L856-L864zh/tutorials/partner-nodes/pricing.mdx#L859-L867
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@tutorials/partner-nodes/pricing.mdx` around lines 817 - 825, Change the EOL
warning and status for gen3a_turbo and the Runway First-Last-Frame node to
future tense, stating that retirement is scheduled for July 30, 2026 rather than
completed. Apply this in tutorials/partner-nodes/pricing.mdx lines 817-825,
ja/tutorials/partner-nodes/pricing.mdx lines 859-867,
ko/tutorials/partner-nodes/pricing.mdx lines 856-864, and
zh/tutorials/partner-nodes/pricing.mdx lines 859-867, preserving the existing
active entries and dates.
| <Warning> | ||
| **End of life (EOL)**: **Runway Gen3a Turbo** and **Runway First-Last-Frame to Video** reached end of life on **July 30, 2026**. Runway retired Gen-3 Alpha Turbo on that date. The related Partner Nodes (`RunwayImageToVideoNodeGen3a`, `RunwayFirstLastFrameNode`) and workflow templates are deprecated and no longer supported. | ||
| </Warning> | ||
|
|
||
| ### 1. Workflow File Download | ||
|
|
||
| The video below contains workflow information in its `metadata`. Please download and drag it into ComfyUI to load the corresponding workflow. | ||
| ### Retired workflows and replacements | ||
|
|
||
| <video | ||
| controls | ||
| className="w-full aspect-video" | ||
| src="https://raw.githubusercontent.com/Comfy-Org/example_workflows/refs/heads/main/api_nodes/runway/gen3a_turbo_image_to_video/runway_image_to_video_gen3a_turbo.mp4" | ||
| ></video> | ||
| | Removed template | Suggested replacement | | ||
| | :--------------- | :-------------------- | | ||
| | `api_runway_gen3a_turbo_image_to_video` | [`api_runway_gen4_turo_image_to_video`](https://github.com/Comfy-Org/workflow_templates/blob/main/templates/api_runway_gen4_turo_image_to_video.json) (Gen4 Turbo) | | ||
| | `api_runway_first_last_frame` | [Kling 3.0 FLF2V](/tutorials/partner-nodes/kling/kling-3-0) (`api_kling_v3_flf2v`) or other first-last-frame templates | |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Do not mark these models retired before July 30, 2026.
Today is July 27, 2026, but all pages say the EOL and template removal already happened on July 30. This prematurely directs users away from still-supported workflows. Time travel belongs in the generated videos.
tutorials/partner-nodes/runway/video-generation.mdx#L15-L24: use future-tense EOL wording, or publish after July 30, 2026.ja/tutorials/partner-nodes/runway/video-generation.mdx#L18-L27: align the Japanese notice and removed-template wording.ko/tutorials/partner-nodes/runway/video-generation.mdx#L18-L27: align the Korean notice and removed-template wording.zh/tutorials/partner-nodes/runway/video-generation.mdx#L18-L27: align the Chinese notice and removed-template wording.
📍 Affects 4 files
tutorials/partner-nodes/runway/video-generation.mdx#L15-L24(this comment)ja/tutorials/partner-nodes/runway/video-generation.mdx#L18-L27ko/tutorials/partner-nodes/runway/video-generation.mdx#L18-L27zh/tutorials/partner-nodes/runway/video-generation.mdx#L18-L27
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@tutorials/partner-nodes/runway/video-generation.mdx` around lines 15 - 24,
Update the Runway retirement notice and removed-template sections so they do not
state that the July 30, 2026 EOL and removals have already occurred before that
date; use future-tense wording while preserving the listed replacements. Apply
the same aligned changes in tutorials/partner-nodes/runway/video-generation.mdx
(15-24), ja/tutorials/partner-nodes/runway/video-generation.mdx (18-27),
ko/tutorials/partner-nodes/runway/video-generation.mdx (18-27), and
zh/tutorials/partner-nodes/runway/video-generation.mdx (18-27), keeping each
translation accurate.
1 participant
Summary
Test plan
translationSourceHashis presentgen3a_turboand legacy Kling models