How QCUL Handles Joomla Core Update Metadata

Joomla core updates are resolved through Joomla Update’s own update-information service rather than pretending core packages are ordinary extension XML updates.

Core metadata behavior

• QCUL calls Joomla Update update-information logic, supporting current signed/TUF-aware metadata or legacy channels that Joomla itself accepts.
• The resolved core target must match the exact target version displayed/selected in QCUL.
• The core ZIP is captured in protected QCUL storage and hashed before the laboratory install.

Why QCUL relies on Joomla

Joomla core update metadata has its own release/channel/security rules. Reusing Joomla’s service means QCUL tests the core package Joomla actually considers valid for that site rather than inventing a parallel core updater.

After capture

The laboratory runtime unpacks the core package with path/symlink safety checks, applies the core tree to the lab, calls Joomla Update finalization/cleanup, and verifies the actual administrator/manifests/files/joomla.xml version.

Keep the evidence chain intact

The value of How QCUL Handles Joomla Core Update Metadata 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.