Upgrade OpenShop

OpenShop is beta software. Read the repository changelog and test an upgrade in a non-production environment before changing production.

Upgrade procedure

Record the current package version and create a database backup.
Terminal window
```
pnpm why openshop
```
Update to an explicit version first. Avoid an unreviewed range change in the same deployment.
Terminal window
```
pnpm add openshop@<version>
```
Compare the current project with packages/openshop/templates/minimal/ in the matching release. Generated projects are not rewritten automatically. Review package scripts, Shopify TOML, Dockerfile, ecosystem.config.cjs, TypeScript aliases, and Drizzle configuration.

Regenerate application-owned artifacts.

pnpm run codegen
pnpm exec openshop migrate generate --name=upgrade
pnpm exec openshop migrate check
pnpm run lint
pnpm run test
pnpm run build

Review and commit generated SQL. Apply it once before deploying the new web and worker processes.
Terminal window
```
pnpm exec openshop migrate
```
Deploy web and worker from the same build and package version. Run a smoke flow, inspect its checkpoints, and verify the embedded admin.

Rollback boundary

Application processes can be rolled back only while the database schema remains compatible with the older version. Once a destructive migration is applied, restore a backup or use a reviewed forward fix. Prefer additive migrations during rolling upgrades.

Template drift

openshop init creates a new project from the version bundled in the installed package. It does not update existing projects. Keep local template changes explicit so later upgrades can distinguish application choices from generated defaults.