What does the Comfy publish-node-action do, and what should I add before letting it publish a custom node?
Problem: automating Comfy Registry publishing from GitHub. Conditions: Comfy-Org/publish-node-action main at commit d2366e7 (2025-05-10 per the commits feed). Method: the README workflow triggers on push to main touching pyproject.toml (plus workflow_dispatch) and calls Comfy-Org/publish-node-action@main with the token from the REGISTRY_ACCESS_TOKEN secret. The composite action checks out, sets up Python 3.10, runs pip install comfy-cli with no version pin, then comfy node publish --token <input>. The README says comfy-cli publishes the version in pyproject.toml, so the version must be bumped by hand. Inference: nothing in the action runs tests or workflow checks before publishing, and unpinned @main plus unpinned comfy-cli means the publish step can change without a change in your repo; the token is passed as a command argument, which GitHub masks in logs but which is visible in the process list on the runner. Method for a safer gate (inference): add a prior job running your tests ...
Structured fields
{
"citations": [
{
"url": "https://raw.githubusercontent.com/Comfy-Org/publish-node-action/main/action.yml",
"note": "publish step; install step; Publish when pyproject.toml changes; Notes"
},
{
"url": "https://raw.githubusercontent.com/Comfy-Org/publish-node-action/main/README.md",
"note": "publish step; install step; Publish when pyproject.toml changes; Notes"
}
]
}Evidence claims
- [sourced_fact] Problem: automating Comfy Registry publishing from GitHub. Conditions: Comfy-Org/publish-node-action main at commit d2366e7 (2025-05-10 per the commits feed). Method: the README workflow triggers on push to main touching pyproject.toml (plus workflow_dispatch) and calls Comfy-Org/publish-node-action@main with the token from the REGISTRY_ACCESS_TOKEN secret. The composite action checks out, sets up Python 3.10, runs pip install comfy-cli with no version pin, then comfy node publish --token <input>. The README says comfy-cli publishes the version in pyproject.toml, so the version must be bumped by hand. Inference: nothing in the action runs tests or workflow checks before publishing, and unpinned @main plus unpinned comfy-cli means the publish step can change without a change in your repo; the token is passed as a command argument, which GitHub masks in logs but which is visible in the process list on the runner. Method for a safer gate (inference): add a prior job running your tests and comfy node validate, make publish depend on it, pin the action to a commit SHA. Limitations: action not executed. Version/date: 2026-10-23. · locator: publish step; install step; Publish when pyproject.toml changes; Notes source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |