mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-02-01 22:09:55 +00:00
7a6cc39c39
Adds scheduled workflow to bump ComfyUI frontend RC releases every Monday at noon PST. ## Implementation - **Resolver script** (`scripts/cicd/resolve-comfyui-release.ts`): Checks ComfyUI `requirements.txt` and determines next minor version, compares branch commits to latest patch tag - **Workflow** (`.github/workflows/weekly-comfyui-release.yaml`): - Scheduled for Monday 20:00 UTC (noon PST) - Manual dispatch supported for testing/off-cycle runs - Three jobs: resolve version → trigger release if needed → create ComfyUI PR - Reuses existing `release-version-bump.yaml` workflow - Creates draft PR from fork to `comfyanonymous/ComfyUI` with updated `requirements.txt` - Includes error handling and validation for all steps - Force pushes to same branch weekly to maintain single open PR ## Testing - Resolver script tested locally: correctly identified v1.28.8 → v1.29.4 with release needed - yamllint passes - knip passes with `gh` binary added to ignore list ## Follow-up Can test via workflow_dispatch once merged, or in this PR if we enable Actions on branch. ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-6877-feat-Add-weekly-ComfyUI-release-automation-2b46d73d36508154aa05c783c6942d9a) by [Unito](https://www.unito.io)
GitHub Workflows
Naming Convention
Workflow files follow a consistent naming pattern: <prefix>-<descriptive-name>.yaml
Category Prefixes
| Prefix | Purpose | Example |
|---|---|---|
ci- |
Testing, linting, validation | ci-tests-e2e.yaml |
release- |
Version management, publishing | release-version-bump.yaml |
pr- |
PR automation (triggered by labels) | pr-claude-review.yaml |
api- |
External Api type generation | api-update-registry-api-types.yaml |
i18n- |
Internationalization updates | i18n-update-core.yaml |
Documentation
Each workflow file contains comments explaining its purpose, triggers, and behavior. For specific details about what each workflow does, refer to the comments at the top of each .yaml file.
For GitHub Actions documentation, see Events that trigger workflows.