mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-06-05 20:54:56 +00:00
43fb5a8b19
## Summary Add `release_type` input (`minor`/`patch`) to the release workflow so patch releases can target the current production branch instead of always preferring the next minor. ## Problem When a patch release is needed for `core/1.42` but `core/1.43` already exists, the resolver always prefers `1.43`. There was no way to do a patch release with PyPI publish + ComfyUI PR for the current production version. ## Changes - Rename workflow from "Release: Bi-weekly ComfyUI" → "Release: ComfyUI" (serves both cadences) - Add `release_type` choice input: `minor` (default, bi-weekly) vs `patch` (hotfix for current production version) - Update `resolve-comfyui-release.ts` to read `RELEASE_TYPE` env var for branch targeting - Scheduled runs continue to work as before (default to `minor`) ## Usage ```bash # Bi-weekly minor release (or just let the schedule run) gh workflow run release-biweekly-comfyui.yaml --ref main # Patch release for current production version gh workflow run release-biweekly-comfyui.yaml --ref main --field release_type=patch ``` ┆Issue is synchronized with this [Notion page](https://app.notion.com/p/PR-11223-ops-add-patch-release-support-to-ComfyUI-release-workflow-3426d73d365081498c15ff978a7f1116) by [Unito](https://www.unito.io)