Skip to content

feat(comfyui-v0.16.4): VisionPlaid 1.2.2 → 1.3.0#93

Open
jackzhao8886 wants to merge 2 commits into
capfrom
feat/vp-1.3.0
Open

feat(comfyui-v0.16.4): VisionPlaid 1.2.2 → 1.3.0#93
jackzhao8886 wants to merge 2 commits into
capfrom
feat/vp-1.3.0

Conversation

@jackzhao8886

Copy link
Copy Markdown
Collaborator

改动

src/code/comfyui/v0.16.4/Makefile(2.x / major 2 版本线):

VISION_PLAID_VERSION 1.2.2 1.3.0
CAP_SYSTEM_VERSION 2.0.3 2.0.4
BITFORGE_VERSION 0.2.4 0.2.4(不变)

为什么 bump CAP_SYSTEM_VERSION

BUILTIN_DEPENDENCY_VERSION = CAP_SYSTEM_VERSION 是存量实例的依赖指纹。VP 版本本身不编码进指纹,所以必须手动 bump CAP_SYSTEM_VERSION,否则存量用户冷启动不会触发重装,升级到不了存量项目。

VP 节点代码

Comfy-VisionPlaid 节点随 pip 包 vision_plaid 自带,构建时 cp -r site-packages/vision_plaid/Comfy-VisionPlaid 拷入,无需手维护版本特化覆盖(v0.16.4/custom_nodes/ 为空)。

后续发版步骤(合并后)

  1. 构建机基于 cap 拉代码 → make build(产出 comfyui:v2.0.4-comfyui-v0.16.4)→ 验证 pip show vision-plaid = 1.3.0
  2. make upload-base → tag source 镜像 funart-comfyui:v2.0.4
  3. make release VERSION=v2.0.9 COMFYUI_VERSION=v0.16.4
  4. 胶水层 config.js + upgrade.js 镜像 tag → v2.0.9,MR → prod 分支
  5. htops 两批预热

🤖 Generated with Claude Code

- VISION_PLAID_VERSION: 1.2.2 → 1.3.0
- CAP_SYSTEM_VERSION: 2.0.3 → 2.0.4(指纹 bump,触发存量实例重装新版 VP)
- bitforge 保持 0.2.4 不变

Change-Id: Ic1f6ad3d2053bd29cfcd87e36afd16ceeb2ec4c5
Co-developed-by: Claude <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: luling.zqj <luling.zqj@alibaba-inc.com>
根 Makefile 有一份独立的 CAP_SYSTEM_VERSION,驱动 make release 的
AGENT_COMFYUI_IMAGE(funart-comfyui:vX) 和 BUILTIN_DEPENDENCY_VERSION。
只改 v0.16.4/Makefile 不够——make release 仍会拉旧 source 镜像 v2.0.3
(含 VP 1.2.2)。两份必须同步 bump。

Change-Id: I45208065279863811a531daf131eb2aacccd660a
Co-developed-by: Claude <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: luling.zqj <luling.zqj@alibaba-inc.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant