Updating

When updating Sonata, protect your local customizations first.

Do not overwrite customized config, product data, or assets without comparing files first.

Before Updating

Commit or back up your current changes.
Note files you customized.
Export important product data.
Check the changelog if available.
Update in a separate branch.

Files Commonly Customized

lib/config/site.ts
app/globals.css
lib/data/game-hosting.ts
lib/data/product-config.ts
components/Navbar.tsx
components/Footer.tsx
public/asset/

Recommended Branch Flow

Use a separate branch for each update:

git checkout -b update/sonata-version

Then apply the new version and compare changes before merging into production.

Compare Carefully

Pay extra attention to:

package.json
Lockfile changes.
Route files under app/.
Shared components.
Config structure changes.
Product data shape changes.
Environment variable names.

Safe Update Flow

Download the latest Sonata version.
Compare changed files.
Reapply custom config carefully.
Reinstall dependencies if package files changed.
Run the dev server.
Run a production build.
Test all product pages.

Dependency Changes

If dependencies changed:

pnpm install

Then run:

pnpm build

If the build fails after an update, read the first TypeScript error and check whether a data shape or component prop changed.

After Updating

Check:

Homepage.
Game hosting pages.
Web hosting page.
App hosting page.
VPS page.
Domain page.
Private nodes page.
Status page.
Support pages.
Light and dark mode.
Billing URLs.
License file.

Do Not Remove License Markers

Updates may include license markers or anti-piracy placeholder changes. Do not remove or tamper with them unless you have written permission.

Update Checklist

Custom brand config preserved.
Custom colors preserved.
Product data preserved.
New required environment variables added.
Navigation still works.
Billing links still work.
Domain lookup still works.
Stock and status APIs still work.
Production build passes.