Update ComfyUI core to v0.3.75

[benceruleanlu]

Updated versions

Component	Version
ComfyUI core	v0.3.75
Frontend	v1.30.6
Templates	v0.7.20
Embedded docs	v0.3.1

┆Issue is synchronized with this Notion page by Unito

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request updates the comfyUI version specified in package.json from 0.3.73 to 0.3.75 within the config.comfyUI section. No other fields, configurations, or application logic are modified.

Changes

Cohort / File(s)	Summary
Version bump package.json	Updated config.comfyUI.version from "0.3.73" to "0.3.75"

Possibly related PRs

• Update ComfyUI core to v0.3.73 #1448: Modified the same config.comfyUI.version property, bumping it to 0.3.73; this PR continues the version progression to 0.3.75.
• Update ComfyUI core to v0.3.72 #1444: Also modified the config.comfyUI.version property in package.json to a different target version.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch core-update-0.3.75

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c83c607 and 2bd0fdb.

📒 Files selected for processing (1)

• package.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: build-and-test-e2e-windows / integration-windows-test
• GitHub Check: build-apple-debug-all / build-macos-debug
• GitHub Check: lint-and-format (macos-latest)
• GitHub Check: lint-and-format (windows-latest)

🔇 Additional comments (2)

package.json (2)

18-18: Version update aligns with PR objectives.

The ComfyUI core version has been correctly updated from 0.3.73 to 0.3.75, matching the stated PR objective. The frontend version (line 14) is already at the target v1.30.6.

---

1-125: All four component updates are correctly included—templates and embedded docs are Python packages managed in separate configuration files.

The PR is complete. Templates (v0.7.20) and embedded docs (v0.3.1) are Python packages managed in:

• scripts/core-requirements.patch (patch file)
• assets/requirements/*.compiled (compiled requirements for each platform: Windows CPU/NVIDIA, macOS)

These are distinct from the npm packages in package.json, which is why they don't appear in that file. The review concern was valid but based on an incomplete search scope—all four components mentioned in the PR description are present in their appropriate configuration files.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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