Skip to content

[Partner Nodes] added 4K resolution for Veo models; added Veo 3 Lite model#13330

Merged
Kosinkadink merged 5 commits intomasterfrom
feat/api-nodes/veo-nodes-update
Apr 21, 2026
Merged

[Partner Nodes] added 4K resolution for Veo models; added Veo 3 Lite model#13330
Kosinkadink merged 5 commits intomasterfrom
feat/api-nodes/veo-nodes-update

Conversation

@bigcat88
Copy link
Copy Markdown
Contributor

@bigcat88 bigcat88 commented Apr 8, 2026

API Node PR Checklist

Scope

  • Is API Node Change

Pricing & Billing

  • Need pricing update
  • No pricing update

If Need pricing update:

  • Metronome rate cards updated
  • Auto‑billing tests updated and passing

QA

  • QA done
  • QA not required

Comms

  • Informed Kosinkadink

@bigcat88 bigcat88 force-pushed the feat/api-nodes/veo-nodes-update branch from aba8129 to 3df99f2 Compare April 8, 2026 19:03
… model

Signed-off-by: bigcat88 <bigcat88@icloud.com>
@bigcat88 bigcat88 force-pushed the feat/api-nodes/veo-nodes-update branch from 3df99f2 to c4c0f14 Compare April 9, 2026 06:39
@bigcat88 bigcat88 marked this pull request as ready for review April 21, 2026 16:33
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 21, 2026

📝 Walkthrough

Walkthrough

The PR modifies the Veo video generation nodes to support the veo-3.1-lite model variant and adds resolution selection (720p/1080p/4k). The MODELS_MAP dictionary was updated with new endpoint mappings. Veo3VideoGenerationNode was refactored to inherit directly from IO.ComfyNode with independent schema and execution logic. Price calculations were revised to factor in model variant, resolution, and audio settings. Runtime validation prevents veo-3.1-lite from operating at 4k resolution. Similar updates were applied to Veo3FirstLastFrameNode. Polling intervals increased from 5.0 to 9.0 seconds across both nodes.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main changes: adding 4K resolution support for Veo models and introducing the Veo 3 Lite model.
Description check ✅ Passed The description includes an API Node PR checklist directly related to the changeset, confirming scope, pricing updates, QA completion, and stakeholder communication.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@comfy_api_nodes/nodes_veo2.py`:
- Around line 274-280: The "resolution" IO.Combo.Input allows selecting "4k" but
the runtime checks only reject lite models; update the model validation that
currently handles veo-3.1-lite and veo-3.0* (the logic around lines 396-419) so
that any veo-3.0 family model is treated like the lite models and 4K is
disallowed; specifically, add veo-3.0* to the conditional that prevents/clears
4k, and when a user-selected resolution is unsupported ensure you either
raise/return a validation error or explicitly set resolution to a supported
default instead of silently dropping the field, referencing the "resolution"
input and the model-check branches that currently only mention veo-3.1-lite.
- Around line 444-454: The code dereferences poll_response.response (assigned to
response) without checking it exists, causing raw AttributeError when poll
completes with no response; update the block around poll_response/response to
first check that poll_response.response is truthy (and if not, handle like other
Veo2 defensive branches by raising a controlled API-node failure that includes
poll_response.error or a clear "no response" message), then proceed to read
response.raiMediaFilteredCount/raiMediaFilteredReasons and response.videos only
after that guard so you avoid AttributeError.
🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9abec78d-6019-43d4-bdbc-fad2e9672a38

📥 Commits

Reviewing files that changed from the base of the PR and between ad94d47 and 2cf2a16.

📒 Files selected for processing (1)
  • comfy_api_nodes/nodes_veo2.py

Comment thread comfy_api_nodes/nodes_veo2.py
Comment thread comfy_api_nodes/nodes_veo2.py
@Kosinkadink Kosinkadink merged commit 1e1d4f1 into master Apr 21, 2026
17 checks passed
@bigcat88 bigcat88 deleted the feat/api-nodes/veo-nodes-update branch April 21, 2026 18:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants