Publishing Versions
Publishing creates a snapshot of your project at a specific point in time. Published versions are immutable, making it safe to deploy to production while you continue editing the development version.
How Versioning Works
Every project has a development version that reflects your latest changes. When you publish, Conduet takes an immutable snapshot of your entire project — workflows, prompts, tools, variables, knowledge base settings, and widget configuration — and tags it with a name you choose. You can keep editing in development without ever touching what's live.
Targeting Versions
When interacting with your agent via the API or deployments, you can target a specific version:
| Version ID | Behavior | Use Case |
|---|---|---|
| "development" | Uses the latest unpublished state | Testing and iteration in the dashboard |
| "production" | Uses the most recently published version | Live deployments, production traffic |
| "ver_xyz789" | Uses a specific version by ID | A/B testing, rollback, auditing |
Pass the versionId field in the request body when calling the Conversations API. Channel deployments are pinned to a specific version ID.
Publishing Workflow
Build & Test
Edit your workflows, prompts, tools, and knowledge base in the dashboard. Test using the widget preview, which always targets the development version.
Publish
Go to the Versions tab and click “Publish”. Enter a version name (e.g., “V3 - Added FAQ playbook”). A snapshot is created immediately.
Deploy
Update your channel deployments to reference the new version, or use “production” targeting which automatically uses the latest published version.
Continue Iterating
Your development version is independent of published versions. Continue making changes without affecting live traffic. Publish again when ready.
Version History
The Versions tab shows a chronological list of all published versions. Each entry displays the version name, ID, and creation timestamp. You can view the snapshot of any version to see exactly what was published. If a new version introduces issues, you can re-deploy an older version by updating the deployment's version ID.
API Access
You can list, inspect, and roll back versions programmatically through the Conduet API — handy for automated release workflows or for keeping a changelog in sync with your other tooling. See the API reference for the full set of version endpoints.