Update principles
- Validate release identity before replacing live application code.
- Verify signed release and artifact metadata where required by the release.
- Create a rollback snapshot before mutation.
- Preserve deployment-specific runtime data and trust configuration.
- Use maintenance mode during mutating operations where required.
- Validate application and database health after activation.
- Fail closed if required validation cannot be completed.
Updater administration
The administrative updater interface can display installed version, update availability, transaction status, database state and rollback readiness. Actions exposed by the interface depend on the updater execution boundary enabled by the installed release.
Before applying an update
- Check status
Confirm the updater transaction state is healthy.
- Review release
Confirm the intended target version and channel.
- Preflight
Validate licence/runtime, database and deployment prerequisites.
- Backup
Ensure the rollback source is complete and verifiable.
- Maintenance window
Plan the update for an appropriate operational period.
- Apply
Execute only through the supported updater workflow.
- Postcheck
Validate version, PHP, database, migrations and application health.
Rollback
A rollback is an operational recovery procedure, not a substitute for normal backups. The rollback source should be verified before it is relied upon.