> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mycryptoserver.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Updates

> Get every new release as a pull request in your own repo

Your repo is an independent copy generated from our template — nobody but you
can touch it. Updates are therefore **opt-in**: install the
**My Crypto Server Updates** GitHub App on your repo, and every new release
arrives as a pull request that *you* review and merge. Skipping this step
breaks nothing — you just won't receive update PRs.

## Enable updates (once)

1. On your post-purchase welcome page, click **Enable automatic updates**.
   (Lost the page? The link in your receipt email reopens it.)
2. GitHub asks you to install **My Crypto Server Updates** — choose
   **Only select repositories** and pick the server repo you created from the
   template.
3. Approve the two permissions (Contents, Pull requests) and confirm.

That's it. The App can open pull requests in that one repo — it never merges
anything itself; you always click the button.

<Note>
  Do this *after* you've created your repo from the template — the install step
  asks you to select it. If you enabled updates from a link other than your
  welcome page, the install can't be matched to your license; redo it from the
  welcome page or email support.
</Note>

## When a release ships

A pull request titled **"Update core to vX.Y.Z"** appears in your repo with
the changelog and the list of changed files. Review it, then click
**Merge pull request**. Vercel sees the push to `main` and redeploys
automatically — same environment variables, new code. Total effort: one click.

<Warning>
  Use the default **"Create a merge commit"** button — not "Squash and merge".
  A regular merge commit is authored by *you*, which is what Vercel's Hobby
  plan wants to see on your production branch. A squashed commit can carry the
  update bot's authorship and get its deployment skipped.
</Warning>

Not ready to update? Just don't merge. Each release PR brings you fully up to
date on its own, so you can skip versions and merge only the latest — close
any older update PRs it supersedes.

## Customizing without losing your changes

An update PR resets the files it touches to the official release. Keep your
customization where updates never look:

* **Environment variables** in Vercel — keys, URLs, chains, confirmations.
* **The dashboard** — integrations, payment providers, email, team. All of it
  is stored in your database, which updates never touch.

If you edit source files directly, a future update touching the same files
will show your edits being removed in the PR diff. Nothing is lost until you
merge — review the diff — but treat direct source edits as something you'll
have to re-apply after updates.

## Stopping updates

Uninstall the App from your repo (**your repo → Settings → GitHub Apps**, or
your account's **Settings → Applications**). Your deployment keeps running on
whatever version you last merged — you simply stop receiving PRs. Reinstalling
from your welcome page re-subscribes you.