> For the complete documentation index, see [llms.txt](https://docs.uibakery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uibakery.io/concepts/source-control/migrate-your-app-model-to-the-latest-version.md).

# Migrating your app model to the latest version

To continuously enhance functionality and improve user experience, new versions of UI Bakery may include app model migrations. These migrations modify the app model stored in your Git repositories. Therefore, a manual app model migration is necessary to ensure smooth development process and to prevent developers from encountering merge conflicts.

{% hint style="warning" %}
App model migration is **not strictly required but highly recommended**. If the migration is not performed immediately following an update, it will be done separately in each branch automatically.

Therefore, all developers will see similar changes in their pull requests until the migration changes are merged into the main branch and subsequently into their individual branches.
{% endhint %}

## To migrate your app model:

1. Start by creating a **new** branch named `migrate-release/0.0.0` from the `main` branch.

   The newly created branch will be automatically migrated by UI Bakery.
2. Commit the changes to the **migration** branch.
3. Create a pull request from the `migrate-release/0.0.0` branch to the `main` branch.
4. Merge the pull request into the `main` branch.
5. Switch back to the `main` branch in UI Bakery and pull the latest changes.
6. Using Git, merge the updated `main` branch into any branches under active development.
7. Go to these development branches and pull the changes.

By following this process, you will ensure that your app model is consistently up-to-date, minimizing the risk of conflicts and maintaining smooth development workflow.


---

# 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.uibakery.io/concepts/source-control/migrate-your-app-model-to-the-latest-version.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.