Publish a user package

Publishing a user package creates a numbered version of it. Draft packages auto-increment their patch version on every save. Publishing locks a clean version with a minor or major version number, making it available to use as a dependency in other packages.

Note: Hub publishing is planned for a future release. Published packages are currently available on the local machine only.

Package versions

A user package starts in draft state. The version number shown in the Library panel (for example, 1.3.7) reflects the current draft. The patch number (the last digit) increments each time you save.

When you publish, you choose how the version number advances:

Published versions always end in .0.

Publish a package

  1. In the Library panel, right-click the user package name.

  2. Select Publish.

    The Publish dialog opens and shows the current draft version.

  3. From the Publish version drop-down list, select the bump type. The list shows the exact version number you'll get:

    • Minor bump → X.Y.0: Increments the minor number and resets the patch to 0.
    • Major bump → X.0.0: Increments the major number and resets minor and patch to 0.
  4. Click Publish.

    The package version in the Library panel updates to the new published version.

Revert a published package to draft

Reverting returns the package to draft state so you can continue editing it. This doesn't delete the package.

  1. In the Library panel, right-click the published package name.

  2. Select Delete.

    The package reverts to draft state. The version number in the Library panel continues from where the draft left off.

Delete a package permanently

  1. In the Library panel, right-click the package name and confirm it's in draft state (its version number ends in a non-zero patch, such as 0.1.5).

  2. Select Delete.

    A confirmation prompt appears.

  3. Confirm the deletion.

    The package and all its graphs are removed from the local disk permanently. This action can't be undone.

Note: Selecting Delete on a published package reverts it to draft; it doesn't delete it. You must revert to draft first, then delete the draft to remove the package entirely.