Skip to main content
V-Run tracks every version of your workflow through a built-in commit history. Committing is the act of publishing — there is no separate deploy step and no environment pipeline to manage.

​
Committing changes

When you are ready to publish a version of your workflow, open the Version Control tab, provide a commit message describing your changes, and click Commit. A commit captures a snapshot of:
  • Main code
  • Test code
  • Requirements
  • Test requirements
  • Config YAML
The moment you commit, the new version becomes the live workflow. API triggers and scheduled runs immediately start using it.

​
Commit history

The Version Control panel shows the full history of commits for a workflow. You can browse previous versions and compare changes with a built-in diff viewer powered by Monaco.

​
Draft vs. published

The editor always works against a draft — your in-progress changes. Those changes are only visible to you and only runnable via the editor’s Run button. External triggers (API and schedule) always use the latest commit, so you can iterate on drafts without affecting production traffic.

​
Restoring a previous version

Need to roll back? Select an earlier commit from the history and restore it — the editor loads that version as the new draft. Commit the restored draft and the previous version is live again. There is no downtime between versions: a new commit replaces the live workflow atomically.