> For the complete documentation index, see [llms.txt](https://sitesbyseth.gitbook.io/sitesbyseth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitesbyseth.gitbook.io/sitesbyseth-docs/reign/free-gift-tiers/updates.md).

# Updating Reign

Reign ships new features and fixes regularly (you're reading the docs for the 2.x line). How you update depends on how the theme got onto your store.

## Which setup do I have?

Go to **Online Store → Themes** and look at your Reign theme card:

* If it shows a **GitHub branch name**, you're on the **auto-update** setup (typical for stores set up by Sites by Seth)
* If not, you installed from a **zip** and update manually

## GitHub auto-update setup

Nothing to do 🎉 — updates are pushed to the connected repository and Shopify syncs them to your theme automatically.

Two things to know:

* **Your content is safe.** Changes you make in the theme editor (section content, settings) are saved to JSON files that sync back to the repository — updates don't stomp your customizations.
* ⚠️ **Don't upload update zips manually** on a GitHub-connected store, and don't disconnect the integration — you'd fork yourself off the update path.

## Zip setup: updating manually

Shopify themes don't self-update, and installing a new zip creates a **separate theme** — your section content does not automatically carry over. So the safe flow is:

1. **Download the new version** from your original purchase link (re-download gets you the latest release)
2. **Online Store → Themes → Add theme → Upload zip file** — the new version lands in your library alongside your live theme
3. **Rebuild your customizations** on the new copy: open it in **Customize** and copy over your settings and section content from the live theme (keep both editors open in two tabs and work top-to-bottom — logo/colors/fonts first, then each template)
4. **Preview thoroughly** — homepage, a product, the cart drawer, mobile
5. **Publish** the new copy. Keep the old theme in your library for a week as a fallback, then delete it

💡 **Practical advice:** on a zip setup, don't chase every release. Update when a changelog entry has something you want, or every few months — and consider asking Sites by Seth about moving to the GitHub setup if you update often.

## Before any update

* **Back up:** on your current live theme, click **⋯ → Duplicate**. Free insurance.
* **Note your app embeds:** apps enabled under theme settings → App embeds need re-enabling on a freshly installed copy.

## Custom code warning

⚠️ If you (or a developer) edited Reign's code files directly, those edits exist only in that theme copy — a new zip won't include them, and on GitHub setups they may conflict with updates. Keep a list of any customizations, and prefer **Custom Liquid** sections/blocks for small additions since their content lives in your section settings and is easy to re-add.

## Where updates are announced

Release notes and support: [sitesbyseth.com](https://www.sitesbyseth.com). The version you're running is shown in the theme editor's theme info (e.g. Reign 2.3.1).


---

# 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, and the optional `goal` query parameter:

```
GET https://sitesbyseth.gitbook.io/sitesbyseth-docs/reign/free-gift-tiers/updates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.