SkillPedia Skills Encyclopedia
中文 EN

Skills 2026-08-20 22:13 UTC

ComfyUI-Agent-Kitv3.2.0

Version [3.2.0] committed by SlavaSextron. Update Category: Routine Updates & Maintenance. Commit details: Restore the frontend pinning caveat I removed, and sharpen it with what the pin actually says. This update performs routine maintenance and minor adjustments.

SlavaSextron 74f5b0b SlavaSexton/ComfyUI-Agent-Kit

CommitRaw commit message

Restore the frontend pinning caveat I removed, and sharpen it with what the pin actually says

RESPONSIBLE FOR: a regression I introduced in this repository earlier today, in the v3.2.0 release.

The KNOWN_ISSUES header used to say that core v0.31.0 pins the 1.48.7 frontend package, so the frontend
release line and the bundled package are not the same number. Rewriting that header for v0.33.1 I dropped the
caveat and left only "Current frontend: v1.51.6", which reads as though updating core gets you that frontend.
It does not, and a reader chasing a frontend fix would have concluded it had reached them.

The corrected statement is stronger than the one I deleted, because the pin turns out not to have moved at
all. requirements.txt carries comfyui-frontend-package==1.48.7 at v0.31.0, v0.32.0 AND v0.33.1 alike, read
from the file at all three tags. So updating core anywhere across that range moves the bundled frontend by
nothing, and the newest frontend, now v1.52.2, is reachable only by asking for it explicitly with
--front-end-version. The machine this was checked on runs core 0.32.0 and frontend package 1.48.7, which is
the pin doing exactly what it says.

The rule the entry now states is the general one: read the pin, not the release feed, before believing a
frontend fix has reached you.

Gates: build_plugin link gate passed, check_counts green, em-dash scan zero.