Nodes/GenAsset/Promote Version In GenAsset
ComfyUI Node

Promote Version In GenAsset

Promote Version In GenAsset — making a version the official one

By steliosot·Created 4 months ago·Updated 3 months ago· 1
Promote Version In GenAsset
    • asset_id
    • version_id
    • status_json
    base_urlhttps://genasset.xyz
    tokenComfyUI/user/genasset.json
    asset_id
    version_id

    You've generated thirty versions of the hero shot. Twenty-nine of them are drafts. One of them is the one. Promote Version In GenAsset is the small ceremony that marks it: it tells the asset "this version is now current," and from that moment on, every load of the asset's current version - and every teammate or agent that depends on it - gets that specific version.

    It's the approval gate of the whole system, and it's why "current" and "latest" are different words in this pack. Latest is just whatever you saved last. Current is what you've chosen. If you've been using Load Current Version For Asset to feed a downstream pipeline, this node is how you control what that pipeline sees, without touching the pipeline.

    How it works

    Under the hood it's a single PATCH to api/v1/assets/{asset_id} with current_version_id set to your version. The server flips the asset's pointer; the version record itself is untouched. That's the elegant bit - promoting doesn't move, copy, or modify the version, it just changes which one the asset calls current. Your history stays exactly as it was, and the "current" label moves to where you point it.

    The outputs echo back asset_id, version_id, and a status_json with the updated asset row so you can confirm the pointer actually moved. It's an output node, so it also writes a success line to the UI.

    Inputs and outputs that matter

    Three required inputs: base_url, token, asset_id, and version_id - the asset to update and the version to promote. Both are UUIDs, and both must be non-empty or the node errors out rather than guess. Get them from your load/save nodes or the web UI.

    There's no confirm switch here, so double-check your inputs before you queue. The good news: promoting is cheap and reversible - promote a different version and the pointer moves again. It's the least destructive of the "authority" nodes in this pack.

    Installation

    In the steliosot/ComfyUI-GenAsset pack. ComfyUI Manager → search GenAsset → install, or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/steliosot/ComfyUI-GenAsset.git
    

    Restart after. No extra dependencies; workspace token in the widget, as GENASSET_WORKSPACE_TOKEN, or in ComfyUI/user/genasset.json.

    Common issues

    • "Paste asset_id." / "Paste version_id." - empty inputs, plain and simple. The node refuses to run half-configured.
    • Load Current Version For Asset doesn't return what you promoted - check that the version you promoted belongs to the asset you promoted it on. A version id from a different asset pointed at that asset is a logical mismatch, and the server may just not resolve it the way you expect. Confirm both UUIDs came from the same asset.
    • You promoted, and nothing visibly changed - that's correct behavior. Promotion is a metadata change, not a render. Verify via status_json's asset row or the web UI rather than expecting a visual result.

    The workflow that makes this node shine: save, compare, promote. You keep your drafts as drafts, and your "approved" version is always one deliberate action away - and always the thing everyone else loads.

    Categorygenasset

    Inputs (4)

    NameTypeDefaultDescription
    base_urlSTRINGhttps://genasset.xyz
    tokenSTRINGComfyUI/user/genasset.json
    asset_idSTRINGAsset id (UUID).
    version_idSTRINGVersion id to set as current.

    Outputs (3)

    NameTypeDescription
    asset_idSTRING
    version_idSTRING
    status_jsonSTRING