● Ship · New versions

Updating
move to a new version safely.

Download the new version, keep your settings and data, rebuild, restart. Your console settings live in the database, not in the code, so they survive an update.

01Where updates come from

Download new versions from your CodeCanyon Downloads page. Every release is listed in the Changelog.

02What to keep

Keep	Why
`server/data/` (or your `PARACHUTE_DATA_DIR`)	Console settings, accounts, history, audit log, fee ledger
`ADMIN_SECRET_KEY`	Reads the encrypted secrets in that database
`.env.local`	Your build settings
Your changed files	Icons in `public/`, texts, colours, `src/admin/manifest.ts`

03Update step by step

Back upCopy server/data/ and .env.local. Optionally export the console configuration (Export / Import).
Unzip the new version next to the old oneDo not unzip over your working folder.
Carry your files overCopy .env.local and server/data/ into the new folder (or keep PARACHUTE_DATA_DIR pointing outside the project, which makes this step unnecessary).
Re-apply your code changesIf you rebranded in the source, compare your changed files with the new ones (a diff tool helps) and apply your changes again.
Install, check, build
```
npm ci
npm run gate
```
Restart the serverStop the old process and start npm run server in the new folder with the same environment. Static sites: upload the new dist/.
CheckConsole → Status passes; /settings in the dApp shows no problems; the status strip shows your fee.

Tip

Keeping your changes in a git repository of your own makes updates much easier: commit the new version on a branch and merge your changes.

04The vendored console

The operator console in vendor/mikodes-admin/ is a copy of the MIKODES Admin Kit. Do not edit it there: fixes arrive with item updates and would overwrite your edits.

05Refresh the build-time data

Between versions you can refresh the stock and pool snapshots yourself (both only read the chain), then build again:

npm run snapshot:stocks
npm run snapshot:pools
npm run build

Updatingmove to a new version safely.