> For the complete documentation index, see [llms.txt](https://edentech.gitbook.io/glover/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edentech.gitbook.io/glover/upgrades/how-to-update.md).

# How to update

When a new version of the project is released, there is going to be 2 folders in the following folders:

![Project folder structure](/files/-Mcn_7OB9LRGprlbxJWP)

As you can see there are 2 zipped files(**New Owners** & **Update Owners**) in each folder.

**New Owners:** This is for new buyer. If you are just buying the project/setting up the project for the first time use the New Owners zipped file.

**Update Owners:** This is for existing users/buyers. This folder will contains the code for new features/bugs fixes. All you have to do is update the content of the Update Owners.zip file to the respectively location of your project.

**Patch Owners:** This is for existing users/buyers that already upgrade to the previous version and needs to only apply the fix in the new released patch. For example if we already release v1.6.63, and we fix some reported issue and release 1.6.63-fix-1. If you have already updated your project to 1.6.63, then you use the patch owners.

**NOTE:** There will be an updating/upgrading guide only if there are changes that needs to be made manually by project owners. Apart from that, all update/upgrade is handle by the project


---

# 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:

```
GET https://edentech.gitbook.io/glover/upgrades/how-to-update.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.