> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/build-and-improve/automate/test-and-publish/publishing-workflows.md).

# Publishing workflows

Publish a Draft Workflow into the version that live traffic, triggers and operator-facing apps can use.

The builder edits a **Draft** Workflow version. Builder Runs and Workflow Tests execute that Draft. Publishing creates a version that production can use.

![The Publish panel showing an active v1.0, the current Draft, the version comment, Publish, Unpublish, Discard draft and version history.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fta1XTfdXDDBdSalW6vnM%2Fpublish-active-draft.png?alt=media)

## Publishing a version

The first publication is fixed at **v1.0**. After that, the current Publish menu offers:

* **Update** — publish a patch update to the current major version;
* **New Version** — publish the next major version.

![The current version choice between an Update patch and a New Version major bump.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2Fx66iC7qWdAMWIQTWWUwz%2Fpublish-version-bump.png?alt=media)

A version comment describes what changed. The Draft becomes **Published** with publication metadata and appears in version history.

Production serves a Workflow version only when it is:

* **Published**;
* **active**;
* the Workflow's **default** version.

The first published version is made the default automatically. The Publish action is unavailable while there are unsaved changes, when the Workflow has no configured trigger, or while another publication is already in progress.

## Publishing can change live infrastructure

Publishing is not only a version label. It can deploy an integration trigger before the publication transaction and synchronise the schedule when the new version becomes the default.

If schedule synchronisation fails, publication is aborted. Treat changes to triggers and schedules as production changes.

## Operator-visible Workflows

Operators see published Workflows with an **APP** trigger through the operator-facing app experience. Drafts remain builder work.

Live runs also use real Workflow Request Inbox handoffs rather than the inline Request UI used in builder tests.

## Before publishing

Test representative cases, verify the external accounts and actions the Workflow can affect, inspect failure paths and check any human handoff with the correct production assignee.

A successful builder test is evidence about the Draft path you exercised. It is not proof that trigger delivery, production assignment or every live-data case will succeed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lleverage.ai/build-and-improve/automate/test-and-publish/publishing-workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.