SF Version Check

This is the node you add to a workflow once and then never think about again - and that's fine. SF Version Check has no inputs and one output: a string that reports the pack's version. As of this writing it returns SF ComfyUI Nodes v1.0.2 (the pyproject.toml says 1.0.7, and the version string is hardcoded, which is its own kind of honesty). It's the ComfyUI equivalent of an --version flag, tucked inside the graph.

Why you'd actually use it

When someone shares an SF workflow and it throws a "node not found" or behaves differently from the docs, the first question is always "which pack version are you on?" This node answers it in one glance - you don't have to dig through pip show or wonder whether Manager updated things in the background. It's also a useful canary: if you're debugging a weird node behavior and the version output has changed since last week, that's your first clue the pack got updated under you. Some teams wire the output into a "show text" node and keep it permanently in their saved workflow templates, which is a nice habit even if it looks like clutter.

How it works

There's no mechanism to speak of. The node reads zero inputs and returns a hardcoded string. That's the whole implementation - RETURN_TYPES = ("STRING",), one output named version. If it ever starts reading from the package metadata instead of a constant, this article will be out of date; today, trust it as a label, not a promise about the installed files on disk.

Installing it

Same as every node in the pack: it ships in SF ComfyUI Nodes from Stillfront. ComfyUI Manager → search "SF ComfyUI Nodes" → Install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Stillfront/comfyui-sf-nodes.git
cd comfyui-sf-nodes
pip install -r requirements.txt

No models, no keys, nothing to download.

Common issues

The only real gotcha is the mismatch between the reported string and the real installed version - the hardcoded v1.0.2 may lag the actual pack release. If you're chasing a bug and the version node hasn't changed, check the pack's GitHub releases rather than trusting the output. And since it's hardcoded rather than derived from the installed package, don't use it as an automated upgrade check; treat it as a quick human-readable stamp.