1.0.0-rc.1 · Release Candidate1 min read
Upgrade Verification
Verify an AutoCore upgrade beyond process restart or an HTTP 200 response.
Verify target version and manifest identity, completed migrations, service health, Redis and Meilisearch connectivity, web/admin/API routing, worker startup, reverse-proxy freshness, installation status, representative anonymous pages, and preserved counts or records.
status and doctor provide useful installer observations, but they do not prove application behavior. A successful restart is also not proof that a migration is compatible with all current data.
Verification
Record each result and compare with the pre-upgrade backup manifest. If a check fails, choose retry, roll-forward, application rollback, or database restore using the decision pages; do not combine them implicitly.
Related articles
Re-Upgrade After RollbackReconcile a successful application rollback with the target release before attempting a re-upgrade.Installation VerificationVerify process, container, migration, dependency, routing, and application readiness after AutoCore installation.Doctor and StatusUse the installer status and doctor commands to distinguish installation state from full service health.