---
url: /docs/en/agentbuff-stack/template-upgrades.md
---
# Template versions and upgrades

Generated products have their own repository, brand, resources and business code. The factory records the template source version in `template.json`; it does not make products share a database or overwrite them automatically.

## Prepare a reviewable upgrade

Commit your product work first. Compare the recorded source version with the intended new template revision. Use the repository's distribution/upgrade reporting workflow to review changed files, configuration contracts, dependencies and migrations. Retain original licenses and provenance.

Separate template changes from product-specific processors, content and provider configuration. Resolve conflicts explicitly. Do not replace a customized product directory with a fresh template copy or reuse new template example prices as real product settings.

## Check compatibility

Run configuration validation, type checks, public page checks and relevant behavioral tests in the product. Rebuild its public site, workspace, emails and API together when public configuration or dictionaries change.

Language upgrades need complete metadata and actual content for every enabled language. English original paths remain stable. Existing user input, ledger notes, audit evidence and queued mail identity are not rewritten by a translation upgrade.

Database migrations are a separate intentional operation against a verified target. Preserve original migration history and use additive changes; never apply optional module migrations merely because the source includes them. Back up and rehearse operational changes before a real environment upgrade.

The current task upgrades only the local template/official site and adds bilingual core guides. No real product or cloud deployment is being performed. Detailed original distribution/upgrade acceptance remains in the [Chinese guide](/agentbuff-stack/template-upgrades).