The release workflow is built around safe selection before installation. The public page should answer whether the release is current, what stability channel it belongs to, which Joomla/PHP versions it supports and whether a package is available.
Recommended steps
- Open the product in the public catalog.
- Read the latest release notes and confirm the stability label matches the target environment.
- Check Joomla and PHP compatibility labels before downloading.
- Download the package only when the release is active and the file is available.
- Install the package in Joomla Administrator through System -> Install -> Extensions.
- After installation, configure the update feed when the extension supports direct Joomla updates.
Release states
- Published releases are visible and can be downloaded when a stored artifact exists.
- Archived releases remain visible for history, but their downloads and update-feed delivery are disabled.
- Private releases are not part of the public frontend.
- Alpha, beta and RC stability labels do not automatically block downloads; they are signals for release maturity.
Verification data
Release pages expose file size and every stored checksum value after a release artifact has been stored: SHA256, SHA384, SHA512 and MD5. Each checksum row includes a copy button so deployment workflows can quickly verify the downloaded package.