Why QCUL Excludes Its Own Active Update from Rehearsal

QCUL excludes its own currently running package update from the laboratory rehearsal list so it does not try to replace the update-safety engine while that same engine is coordinating the test.

Why self-update rehearsal is special

The active QCUL component, runtime endpoints, task/system plugins, schema, and AJAX workflow are part of the infrastructure performing laboratory and production operations. Testing the currently executing QCUL update through itself would create ambiguous runtime/version ownership during the operation.

How to update QCUL

Use QC Update Laboratory → Status or Joomla’s normal extension updater to update QCUL itself. After the update, verify the installed version/status and then create/refresh a laboratory before resuming site-update rehearsals.

Do not bypass the exclusion

If a QCUL package is not shown under Test Updates, that is expected product behavior. Installing a QCUL update manually inside the active lab does not create a supported QCUL rehearsal record for a production push.

Keep the evidence chain intact

The value of Why QCUL Excludes Its Own Active Update from Rehearsal depends on preserving one traceable transition: known starting version, one selected update, exact captured package/hash, resulting laboratory version, automated evidence, and human review. Avoid manual package installs or unrelated lab changes that make that chain ambiguous before a production decision.

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.