comfyui-mcp 0.50.88 → 0.50.89

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "comfyui-mcp",
-  "version": "0.50.88",
+  "version": "0.50.89",
   "mcpName": "io.github.artokun/comfyui-mcp",
   "description": "Local-first, agent-native control plane for ComfyUI — MCP server + autonomous sidebar agent that drives your live graph in natural language on ANY LLM: Claude/ChatGPT/Gemini on your subscription (no API key), free local models via Ollama (fully offline), or any hosted model via an OpenAI-compatible endpoint (DeepSeek, GLM, MiMo, OpenRouter). Generate images, video & audio, author and run workflows, manage models and custom nodes; a compact tool-router mode keeps even 4B models effective, and a built-in LLM Arena benchmarks them on real ComfyUI tasks. Also a Claude Code plugin with skills, slash commands, and installer packs. Local, LAN, VPS, or Comfy Cloud.",
   "homepage": "https://comfyui-mcp.artokun.io/docs",

package/scripts/gen-changelog.mjs

@@ -77,7 +77,8 @@ function prevTag() {
  *  squash-merge form GitHub writes from a PR titled with the bare version — `0.49.6 (#849)`.
  *  Only the first was recognised, so the second fell through to the non-conventional
  *  path and was silently dropped along with everything else there. */
-const isReleaseSubject = (s) => /^release:/i.test(s) || /^v?\d+\.\d+\.\d+\s*(\(#\d+\))?$/.test(s);
+// #1309 — three shapes are needed; see scripts/lib/release-subject.mjs.
+import { isReleaseSubject } from "./lib/release-subject.mjs";
 
 /** Parsed commits since `range`, newest-first, minus noise.
  *

package/scripts/lib/release-subject.mjs

@@ -0,0 +1,41 @@
+/**
+ * Is this commit subject a RELEASE, rather than something a release contains?
+ * (#1309)
+ *
+ * Three shapes, and the third is the one this repo produces on EVERY release —
+ * `npm version patch -m "chore(release): %s"`, squash-merged with the PR number
+ * appended by GitHub:
+ *
+ *   release: v0.50.87 — …            a hand-written release PR
+ *   0.50.85 (#1302)                  a bare version subject
+ *   chore(release): 0.50.85 (#1302)  what the release flow actually writes
+ *
+ * Only the first two were matched, so every release-reconcile commit fell
+ * through to the conventional-commit parser, was read as a `chore` with scope
+ * `release`, and appeared in the NEXT release's entry under "Changed".
+ *
+ * Nothing else caught it: the de-duplication that makes the deliberately-wide
+ * commit range safe is "filter out PRs the changelog already documents", and a
+ * release-reconcile PR is never documented — it is not a change.
+ *
+ * TWO CONSTRAINTS, and the second was a codex finding. Scope alone is not
+ * enough: `fix(release): prevent failed releases from corrupting user installs`
+ * is scoped `release` and is a REAL user-facing change. Matching on scope alone
+ * would have silently dropped it — the exact failure this generator warns about
+ * at length, introduced while fixing a different one. So a release-scoped
+ * subject must ALSO carry nothing but a version (plus the PR number GitHub
+ * appends), which is what the release flow produces and what a fix to the
+ * release process never does.
+ *
+ * And deliberately NOT a blanket `chore:` skip, for the same reason in the other
+ * direction: an ordinary chore can be user-facing.
+ *
+ * Lives in its own module so it can be tested directly. An earlier attempt tested
+ * it through the generator against a scratch repo and the test passed with the fix
+ * REVERTED — the synthetic history dropped the entry for an unrelated reason, so
+ * it was verifying nothing.
+ */
+export const isReleaseSubject = (s) =>
+  /^release:/i.test(s) ||
+  /^v?\d+\.\d+\.\d+\s*(\(#\d+\))?$/.test(s) ||
+  /^\w+\(release\)!?:\s*v?\d+\.\d+\.\d+\s*(\(#\d+\))?$/i.test(s);