[GH-ISSUE #1021] [DevTask] Revert workarounds implemented for 0.4.27 release #269

Closed
opened 2026-10-31 22:10:55 +00:00 by bsakaguchi · 3 comments
Owner

Originally created by @webfiltered on GitHub (Mar 5, 2025).
Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1021

Workarounds must be reverted when core has been patched to bypass frontend checks.

┆Issue is synchronized with this Notion page by Unito

Originally created by @webfiltered on GitHub (Mar 5, 2025). Original GitHub issue: https://github.com/Comfy-Org/desktop/issues/1021 Workarounds must be reverted when core has been patched to bypass frontend checks. - #1020 - #1024 ┆Issue is synchronized with this [Notion page](https://www.notion.so/Issue-1021-DevTask-Revert-workarounds-implemented-for-0-4-27-release-1ad6d73d365081debd68ce9757b7954b) by [Unito](https://www.unito.io)
Author
Owner

@dosubot[bot] commented on GitHub (Jun 4, 2025):

Hi, @webfiltered. I'm Dosu, and I'm helping the desktop team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • The issue involves reverting workarounds from the 0.4.27 release due to frontend checks.
  • These workarounds are planned to be removed once the core is patched.
  • The issue is linked to issues #1020 and #1024 and tracked via a Notion page through Unito.
  • No comments or additional activity have occurred since the issue was opened.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the desktop repository by commenting here.
  • If no updates are provided, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

<!-- gh-comment-id:2940582684 --> @dosubot[bot] commented on GitHub (Jun 4, 2025): Hi, @webfiltered. I'm [Dosu](https://dosu.dev), and I'm helping the desktop team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - The issue involves reverting workarounds from the 0.4.27 release due to frontend checks. - These workarounds are planned to be removed once the core is patched. - The issue is linked to issues #1020 and #1024 and tracked via a Notion page through Unito. - No comments or additional activity have occurred since the issue was opened. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of the desktop repository by commenting here. - If no updates are provided, the issue will be automatically closed in 7 days. Thank you for your understanding and contribution!
Author
Owner

@webfiltered commented on GitHub (Jun 5, 2025):

Still in use; review again later.

<!-- gh-comment-id:2942245435 --> @webfiltered commented on GitHub (Jun 5, 2025): Still in use; review again later.
Author
Owner

@dosubot[bot] commented on GitHub (Sep 4, 2025):

Hi, @webfiltered. I'm Dosu, and I'm helping the desktop team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested reverting the 0.4.27 release workarounds once the core is patched to bypass frontend checks.
  • The issue references related issues #1020 and #1024 for context.
  • I previously marked this issue as stale due to inactivity and asked if it was still relevant.
  • You confirmed the workarounds are still in use and requested a later review.
  • No further updates have been provided since your last confirmation.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of the desktop app by commenting here.
  • If I do not hear back within 7 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

<!-- gh-comment-id:3254415954 --> @dosubot[bot] commented on GitHub (Sep 4, 2025): Hi, @webfiltered. I'm [Dosu](https://dosu.dev), and I'm helping the desktop team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested reverting the 0.4.27 release workarounds once the core is patched to bypass frontend checks. - The issue references related issues #1020 and #1024 for context. - I previously marked this issue as stale due to inactivity and asked if it was still relevant. - You confirmed the workarounds are still in use and requested a later review. - No further updates have been provided since your last confirmation. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of the desktop app by commenting here. - If I do not hear back within 7 days, this issue will be automatically closed. Thank you for your understanding and contribution!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Comfy-Org/desktop#269
No description provided.