mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-05-05 21:54:50 +00:00
46dad2e077
## Summary Restrict PyPI publishing of `comfyui-frontend-package` to bi-weekly ComfyUI release cycles only, instead of every nightly version bump. ## Changes - **What**: Move `publish_pypi` job from `release-draft-create.yaml` to `release-biweekly-comfyui.yaml` 1. Removed `publish_pypi` job from `release-draft-create.yaml` (no longer publishes on every merged Release PR) 2. Added `publish-pypi` job to `release-biweekly-comfyui.yaml` with tag polling, build, publish, and PyPI availability confirmation 3. Gated `create-comfyui-pr` on `publish-pypi` success so the ComfyUI requirements bump PR is only created after the package is confirmed available 4. Updated ComfyUI PR body to confirm PyPI availability instead of warning about a pending release PR - **Breaking**: None — nightly releases still create GitHub releases and publish npm types; only PyPI publishing timing changes - **Dependencies**: None ## Review Focus - The `publish-pypi` job uses `if: always() && needs.resolve-version.result == 'success'` to run even when `trigger-release-if-needed` is skipped (tag already exists) - Tag polling (30min timeout) waits for the version bump PR to be merged before building from the tagged commit - PyPI propagation polling (15min timeout) confirms the package is installable before creating the ComfyUI PR Fixes COM-16778 ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-9948-ops-restrict-PyPI-publishing-to-bi-weekly-ComfyUI-releases-3246d73d36508198b00fcc247ac5b58c) by [Unito](https://www.unito.io) --------- Co-authored-by: GitHub Action <action@github.com>
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.