Core Updates and Recovery
Check eligibility and prepare
Section titled “Check eligibility and prepare”Start with CLI setup and verification. The updater requires a CLI installation receipt. Keep the receipt created by CLI setup intact. Downgrades, framework/variant migration and automatic peer dependency upgrades are not implemented.
Back up your project. Stop dev servers and tools that write dependencies before applying. The CLI coordinates other CLI updaters, but cannot lock every editor or external tool.
Preview an update
Section titled “Preview an update”Preview the changes before applying:
npx @rtthemes/cli@latest update --project /path/to/customer-project --dry-runApprove access in your Dashboard browser. Select an authorized newer version and inspect the file/dependency plan. --to VERSION selects a particular newer version. Dry-run does not apply changes or run project scripts, but still requires authorization. An already-current update also checks account access.
The current delivery protocol does not provide a separate changelog/breaking-migration field. Read the release notes supplied through the product’s release channel; the CLI does not perform an automatic migration review.
Apply the core update
Section titled “Apply the core update”npx @rtthemes/cli@latest update --project /path/to/customer-projectThe managed changes are limited to:
- The new versioned core archive under
vendor/. - The core dependency in
package.jsonand matching npm lockfile. - The matching
.rtthemes/kit.jsonand installation receipt.
Old vendor archives are retained. Customer pages, MDX/JSON content, settings, images, local components, configuration, scripts and other dependency declarations are preserved. The new starter is never unpacked over your edited website. The original delivery inventory stays historical evidence, not a reset list.
Before applying, the CLI runs install/check/build on a private copy of the actual project. It excludes .env*, .npmrc, Git, installed dependencies and generated build/cache directories. Supply required configuration through your normal environment; a project that requires excluded files or incompatible peer versions stops for review. These are your project’s scripts, not a security-isolated execution service.
Passing check/build does not guarantee that customized component copies still work. Check them and your connected services after updating.
Recover an interrupted update
Section titled “Recover an interrupted update”The updater keeps verified backups and a private transaction journal. If it reports an unfinished operation, retain those files and run offline recovery:
npx @rtthemes/cli@latest update --project /path/to/customer-project --recoverRecovery verifies backups and refuses to overwrite later customer edits or unknown dependency-directory changes. Preserve the workspace when it asks for manual review. If the update already committed but cleanup was interrupted, recovery finishes cleanup instead of downgrading.
Do not delete the journal or edit its hashes to force completion. See the NaturaLife Astro update guide for product-specific checks after a CLI update.