> For the complete documentation index, see [llms.txt](https://search.docs.reactify.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://search.docs.reactify.com.au/guides/upgrade-workflow.md).

# Upgrade workflow

### Basic workflow

1. Install the latest version of `@usereactify/search` package.

```
npm install @usereactify/search@latest
```

### Git workflow

The instructions below apply to most people who use Git and a CI/CD process for deploying preview builds.

1. Clone the stores frontend repository and checkout the `master` or `main` branch.

```
git clone git@gitlab.com:foobar/foobar-website.git
git checkout master
```

2. Find where the `@usereactify/search` package is installed, for theme-based websites it's usually in the root and for headless it's usually in the `app` folder.

```
cd app
```

3. Install the latest version of `@usereactify/search` package.

```
npm install @usereactify/search@latest
```

4. Create a new branch, stage the changes, commit the changes and push to the remote repository

```
git checkout -b feature/upgrade-reactify-search
git add .
git commit -m "feat: upgrade reactify search"
```

5. Visit the remote repository online and submit a pull request.

Allow CI/CD processes to create a preview builds, review the preview and if there are no issues merge the pull request.


---

# 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://search.docs.reactify.com.au/guides/upgrade-workflow.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.