Pushing a Tested Extension Update to Production Step by Step

A production extension push reuses the exact package that completed the private laboratory workflow and stops if current production preconditions no longer match the tested plan.

Step-by-step procedure

  1. Finish the exact extension update test and human laboratory review.
  2. Choose production protection.
  3. Select Push to Production.
  4. QCUL rechecks the exact package hash, expected installed version, production identity, permissions, storage/environment, worker state, review confirmation, and recovery choice.
  5. If a temporary checkpoint is selected, wait for it to complete before install.
  6. QCUL installs the same tested package with Joomla Installer and verifies the target version/routes.
  7. Open Review Live Site, verify the production site, retain the updated report, and use Undo Production Push promptly if a serious issue is found and a valid QCUL checkpoint exists.

Production evidence remains attached

After the push, the tested row stays visible with live result/validation, Review Live Site, Download Report, and eligible undo controls. The current Joomla update cache does not have to keep the row alive for QCUL to retain its maintenance record.

Production change rule

For Pushing a Tested Extension Update to Production Step by Step, the live site should change only through the explicit tested-item production workflow after current readiness checks pass. Do not substitute a new package, skip the review/protection decision, or run a second production action while QCUL already owns an active push/rollback state.

Community Discussion

Want to compare update-testing workflows, share practical tips, or discuss how you use this QCUL feature? Visit the QC Update Laboratory Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.