feat: add toggle to control ComfyUI version-update notifications (default off)#1205
feat: add toggle to control ComfyUI version-update notifications (default off)#1205Kosinkadink wants to merge 3 commits into
Conversation
Adds a 'Show ComfyUI version updates' toggle (Updates settings, default on) that injects the show_version_updates feature flag into the embedded ComfyUI at launch, seeding its Comfy.Notification.ShowVersionUpdates default. Lets Desktop users suppress the in-frontend release notifications in favor of Desktop's own update UI; the ComfyUI setting still overrides. Only injected when the running ComfyUI advertises the flag. Amp-Thread-ID: https://ampcode.com/threads/T-019f0347-dc00-723a-a4d2-558539329035 Co-authored-by: Amp <amp@ampcode.com>
|
Warning Review limit reached
More reviews will be available in 59 minutes and 49 seconds. Learn how PR review limits work. To continue reviewing without waiting, enable usage-based billing in the billing tab. ⌛ How to resolve this issue?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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughAdds a ChangesComfyUI version-update setting
Sequence Diagram(s)sequenceDiagram
participant "launch.ts"
participant "settings.get"
participant desktopFeatureFlags
participant "ComfyUI frontend"
"launch.ts"->>"settings.get": read showComfyVersionUpdates
"launch.ts"->>desktopFeatureFlags: pass showVersionUpdates boolean
desktopFeatureFlags->>"ComfyUI frontend": inject show_version_updates
Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ 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 |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai full review |
✅ Action performedFull review finished. |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
Caution Failed to replace (edit) comment. This is likely due to insufficient permissions or the comment being deleted. Error details |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai review |
✅ Action performedReview finished.
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@src/main/popups/titlePopup.ts`:
- Around line 2074-2082: The filtering in titlePopup.ts duplicates the same
update-field IDs in both desktopUpdateFields and generalFields, which risks the
sections drifting apart when another toggle is added. Extract the update-related
IDs into one shared symbol near the generalRaw filters, then have both the
desktopUpdateFields and generalFields predicates reference that shared set so
the grouping logic stays consistent.
🪄 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: 41361887-f045-401a-9274-737c6257500f
📒 Files selected for processing (7)
locales/en.jsonlocales/zh.jsonsrc/main/lib/ipc/registerSettingsHandlers.tssrc/main/lib/ipc/sessionActions/launch.test.tssrc/main/lib/ipc/sessionActions/launch.tssrc/main/popups/titlePopup.tssrc/main/settings.ts
Amp-Thread-ID: https://ampcode.com/threads/T-019f0347-dc00-723a-a4d2-558539329035 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019f0347-dc00-723a-a4d2-558539329035 Co-authored-by: Amp <amp@ampcode.com>
|
Still need to test end-to-end |
christian-byrne
left a comment
There was a problem hiding this comment.
LGTM but it would make sense to use the same settings key as the frontend for this IMO.
Fixes #1194
Adds a Show ComfyUI version updates toggle (Updates settings tab, default off) that injects the
show_version_updatesfeature flag into the embedded ComfyUI at launch. The flag seeds the frontend'sComfy.Notification.ShowVersionUpdatesdefault. Comfy Desktop has its own update / What's-New UI, so the in-frontend release notifications are off by default; a user can opt in via this toggle. The ComfyUI setting still overrides it.Changes
settings.ts— newshowComfyVersionUpdatessetting (default off).desktopFeatureFlags()— injectsshow_version_updates=<bool>from the setting.registerSettingsHandlers.ts/titlePopup.ts— render the toggle in the Updates tab (with a shared field-id set so the snapshot grouping can't drift).locales/en.json+locales/zh.json— labels/description.The flag is only injected when the running ComfyUI advertises it via
--list-feature-flags(existing registry guard), so it is a no-op on older ComfyUI.Cross-repo dependencies
show_version_updatesflag (default off).