> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/releases-and-environments/saved-changes-versions-and-published-releases.md). # Saved Changes, Versions, and Published Releases Saved edits, saved versions, and published releases serve different purposes. Use version history to identify the configuration that users actually run. {% embed url="" %} ## Before you begin Permission to edit the project and view its release history. ## Drafts, versions, and releases | Term | Definition | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | Draft | The editable project configuration before or apart from a selected published release. Saving a draft does not necessarily change what published users run. | | Project version | A specific saved configuration of a project. Select it explicitly when a result must be reproducible. | | Published release | The selected project version made available through a published execution path. Confirm the active release after a publication or promotion action. | | Release request | A request for review of a proposed project release. Check the version and destination covered by the request before approval. | ## Confirm your saved draft and publish a version 1. Make your intended edits. StackAI autosaves the working draft in Workflow Builder, Interface, and Agent Builder. Check the save indicator and last confirmed save time, then review the workflow and interface. Resolve any save error or concurrent-edit message before continuing. ![The saved timestamp confirms that the working draft has been saved.](https://1957915746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FoUso4U8gMce8pYg09nz5%2Fautosave-saved-timestamp.png?alt=media\&token=c197b16c-6757-445a-ad17-44dbfec5d5fd) For the save indicator and both conflict-resolution choices, see [Autosave and concurrent editing](/technical-reference/releases-and-environments/autosave-and-concurrent-editing.md). 2. Create or select the version required by the release process. 3. Publish or promote it through the project’s supported controls and confirm the active release. The intended version is available through the selected execution path. ## Behavior and limitations Autosave updates your editable draft; it does not make that draft live or replace the active published release. When publishing, StackAI first saves pending draft changes. A saved historical version remains distinct from the current editable workflow. Record the selected version when reproducing a result. Projects with release approval use their approval and promotion process rather than bypassing it with a different publication path. ## Related resources [Autosave and concurrent editing](/technical-reference/releases-and-environments/autosave-and-concurrent-editing.md) [Project version history and diffs](/guides-and-quickstarts/releases-and-environments/project-version-history-and-diffs.md) [Environment Variables and Secrets](/technical-reference/releases-and-environments/environment-variables-and-secrets.md) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stackai.com/technical-reference/releases-and-environments/saved-changes-versions-and-published-releases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.