[GH-ISSUE #3272] CNR 插件版本比較使用字串比較而非數值比較，導致高版本被標記為衝突 #1131

New issue

Open

opened 2026-10-27 21:26:02 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-27 21:26:02 +00:00

Owner

Originally created by @ping13579246810 on GitHub (Sep 11, 2026).
Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/3272

問題描述

當 ComfyRegistry 中某個插件的已安裝版本比 registry 記錄的最新版本更新時，ComfyUI-Manager 會錯認地將已安裝版本標記為「衝突」。

經診斷，這是因為 Manager 使用字串比較而非數值比較來比對版本號。

複現步驟

安裝 minimax-h3-audio-t8 v1.78.1
ComfyRegistry 記錄的最新版本是 1.47.0
Manager 認為 1.47.0 > 1.78.1（字串比較錯誤）
顯示衝突警告

预期行為

應認使用 packaging.version.parse() 或類似方法進行數值版本比較：

1.78.1 > 1.47.0 ✅ 正確
字串比較: "1.47.0" > "1.78.1" ❌ 錯誤

影響範圍

所有 ComfyRegistry (CNR) 插件都可能受此影響，特別是當註冊版本落後於實際 GitHub 版本時。

建議修復

在 Manager 的版本比較邏輯中使用 semantic versioning 比較庫（如 Python 的 packaging 套件）。
以上由AI代筆整理

Originally created by @ping13579246810 on GitHub (Sep 11, 2026). Original GitHub issue: https://github.com/Comfy-Org/ComfyUI-Manager/issues/3272 ## 問題描述當 ComfyRegistry 中某個插件的已安裝版本比 registry 記錄的最新版本更新時，ComfyUI-Manager 會錯認地將已安裝版本標記為「衝突」。經診斷，這是因為 Manager 使用**字串比較**而非**數值比較**來比對版本號。 ## 複現步驟 1. 安裝 minimax-h3-audio-t8 v1.78.1 2. ComfyRegistry 記錄的最新版本是 1.47.0 3. Manager 認為 1.47.0 > 1.78.1（字串比較錯誤） 4. 顯示衝突警告 ## 预期行為應認使用 `packaging.version.parse()` 或類似方法進行數值版本比較： - `1.78.1 > 1.47.0` ✅ 正確 - 字串比較: "1.47.0" > "1.78.1" ❌ 錯誤 ## 影響範圍所有 ComfyRegistry (CNR) 插件都可能受此影響，特別是當註冊版本落後於實際 GitHub 版本時。 ## 建議修復在 Manager 的版本比較邏輯中使用 semantic versioning 比較庫（如 Python 的 `packaging` 套件）。以上由AI代筆整理

bsakaguchi commented

2026-10-27 21:26:03 +00:00

Author

Owner

@T8mars commented on GitHub (Sep 14, 2026):

Maintainer note for the example node: the semantic-version comparison problem described here is valid, but minimax-h3-audio-t8 currently also has a separate Registry state problem. Versions through 1.80.0 were uploaded, but 1.80.0 is NodeVersionStatusFlagged with extraction pending, so the node API genuinely exposes 1.47.0 as the latest Active version.

That separate Registry review is tracked at:
https://github.com/Comfy-Org/registry-backend/issues/233

Fixing semantic version comparison will prevent an installed 1.78.1 from being ordered incorrectly against 1.47.0, while the Registry review is still required before Manager can discover 1.80.0 as the current installable version.

@T8mars commented on GitHub (Sep 14, 2026): Maintainer note for the example node: the semantic-version comparison problem described here is valid, but `minimax-h3-audio-t8` currently also has a separate Registry state problem. Versions through 1.80.0 were uploaded, but 1.80.0 is `NodeVersionStatusFlagged` with extraction `pending`, so the node API genuinely exposes 1.47.0 as the latest Active version. That separate Registry review is tracked at: https://github.com/Comfy-Org/registry-backend/issues/233 Fixing semantic version comparison will prevent an installed 1.78.1 from being ordered incorrectly against 1.47.0, while the Registry review is still required before Manager can discover 1.80.0 as the current installable version.