> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/settings/publishing/app-version-history.md).

# App Version History

Restore or publish a previous app version

{% hint style="info" %}
App version history is available on the Build and Enterprise plans.
{% endhint %}

Noloco's App Version History feature lets you revert your current project draft to a previous version or publish a previous version to your users. **You can browse and restore any saved version with ease.**

### Restore a previous version

1. Enter **Builder mode**
2. Click the **Publish** button in the top right
3. Select **Version History**
4. Find the version you want to restore from the list
5. Click the **⋮** menu next to that version
6. Choose **Publish this version** or **Revert editor to this version**
7. Click **Done**

#### **Which option should I use?**

* **Publish this version:** the selected version goes live immediately for your users. Builders will continue to see the current draft, which remains unchanged.
* **Revert editor to this version:** restores your current draft to the selected version. Your unpublished changes will be overwritten, and other builders will immediately see the updated draft.

**Need to undo a revert?** You can always return to any version in your history.

{% @arcade/embed url="<https://app.arcade.software/share/ryulJA7cbzJkFCShD0Tb>" flowId="ryulJA7cbzJkFCShD0Tb" %}


---

# 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://guides.noloco.io/settings/publishing/app-version-history.md?ask=<question>&goal=<user_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.