How to Version and Deploy Transformations Beta

Save transformation drafts, publish versioned changes, and deploy older transformation versions.

This guide covers how to:

  • Save unpublished transformation changes as drafts
  • Publish tagged versions for production use
  • Deploy an older version when you need to roll back

For draft and version behavior in libraries, see Version and publish libraries.

Save a transformation draft

  1. Open the transformation in the RudderStack dashboard and go to the Editor tab.
  2. Update the transformation code.
  3. Click Save draft.
Save draft button for a transformation

To discard unpublished edits, click Discard changes. The editor reverts to the version you opened for editing.

Important considerations

  • Transformation drafts cannot go to production: Destinations always run the published Active transformation version. You cannot connect a transformation that has never been published.
  • Draft changes are not published: If a transformation is already connected to destinations, they continue to use the Active published version until you publish or deploy a different transformation version.

After you save a draft, the transformation shows Unpublished changes in the header and a Draft badge in the editor.

Transformation with unpublished draft changes

Publish a new transformation version

You can publish a new version directly — you don’t need to save a draft first.

  1. In the Editor tab, click Publish.
  2. In the Publish new version modal, enter a Tag for the version. The modal shows the latest tag used so you can choose the next one.
  3. Optionally add a Description of your changes.
  4. Click Publish.
Publish new transformation version modal
Publishing a new version makes it Active immediately. Destinations connected to this transformation start using the new code for newly ingested events.

View version history

  1. Open the transformation and go to the Versions tab.
  2. Select a version in Version history to preview its code, tag, description, author, and timestamp.

The Active badge marks the version currently used in production.

Transformation version history with Active version

To edit from a specific version without changing the Active version:

  1. Select the version in Version history.
  2. Click Open in editor.

The editor loads that version’s code into a draft. The active version stays unchanged until you publish a new version or deploy an older version.

Deploy an older transformation version

You can make a previously published version Active again. This is helpful when you need to roll back to a previous version due to a bug in the current active version.

  1. Open the transformation and go to the Versions tab.
  2. Select the older version you want to deploy. Deploy is available for non-Active versions.
Deploy button for an older transformation version
  1. Click Deploy.
  2. In the Replace active version? modal, review the impact, then click Validate & Continue. Your test cases are validated against the selected version’s code.
Replace active version confirmation modal
  1. Complete deployment based on the test results:
  • If all tests pass, click Deploy Now.
Deploy transformation modal when all tests pass
  • If any tests fail, review the failures. You can click Deploy Anyway to proceed, or Cancel to fix the issues first.
Deploy transformation modal when some tests fail
Deploying with failing tests can cause data discrepancies or processing errors. Fix failing tests before you deploy when possible.

After a successful deploy, the selected version shows the Active badge. Connected destinations use that version for newly ingested events.

See more

Questions? Let's figure it out together.

Join the RudderStack Slack community to connect with other users, customers, and the RudderStack team — or reach out for direct support.