Cloning & Versioning

Plugins use a version-based workflow where published versions are locked and new work happens on cloned versions. This keeps published plugins stable while allowing continuous iteration.

How Versioning Works

Each plugin can have multiple versions. Every version has a status:

Status	Description
Unpublished (Draft)	Editable — you can modify YAML, parameters, and settings
Published	Read-only — locked and available for use in scenarios

When you publish a version, it becomes read-only. To make further changes, you create a new version by cloning.

Version Dropdown

The plugin editor shows a version dropdown at the top. From here you can:

• Switch between versions to view their YAML and configuration
• See which versions are published vs. draft
• See who last modified each version and when

Two Types of Cloning

Duplicate to New Version

Creates a new version within the same plugin. Use this to iterate on an existing plugin:

• Copies all YAML, parameters, dependencies, automated actions, and resources
• Creates a new draft version with an incremented version number
• The new version appears in the same plugin’s version dropdown
• Previous published versions remain available for use

When to use: You want to improve or update a plugin you own.

Clone to New Plugin

Creates an entirely new, independent plugin from an existing one. Use this when:

• You want to customize someone else’s plugin for your own use
• You want to fork a plugin in a different direction
• You’re starting from an existing plugin as a template

The cloned plugin:

• Gets its own name and identity
• Has no version link back to the original
• Starts as a draft you fully own
• Copies all YAML, parameters, dependencies, and configuration

When to use: You want to build on someone else’s plugin or create a variant.

Note

Cloning requires clone permission on the source plugin. Check Plugin Permissions for details.

Publishing and Unpublishing

Publishing a Version

1. Ensure your YAML is saved and tested
2. Click Publish in the toolbar
3. Add a changelog entry describing what this version does
4. The version becomes read-only and available for use in scenarios

Unpublishing a Version

You can unpublish a version to return it to draft status. This makes it editable again but removes it from availability in the Plugin Browser.

Caution

Unpublishing a version that’s actively used in scenarios may affect those scenarios. Scenario builders who already have the plugin applied will keep their current configuration, but new users won’t be able to add it until it’s republished.

Time Machine

The Time Machine provides a historical view of your plugin’s YAML at any point in time.

How It Works

Every time you save your YAML, the system records a snapshot. The Time Machine lets you:

1. Click the clock icon in the editor
2. Browse snapshots by date
3. View the YAML as it existed at that point (read-only)
4. Compare with the current version

This is useful for reviewing how a plugin evolved over time or recovering a previous approach.

YAML History

Each version tracks its own save history. The history dropdown shows timestamps for each saved snapshot. Selecting a snapshot opens it in a read-only diff view so you can compare it against the current YAML.

Iteration Workflow

The typical iteration cycle for a published plugin:

1. Duplicate to New Version — creates a new draft from the published version
2. Edit — modify YAML, update parameters, adjust dependencies
3. Test — add the draft version to a scenario and build
4. Publish — lock the new version and make it available
5. Repeat — clone again when you need more changes

Each published version has its own changelog entry, building a history of the plugin’s evolution.