Prepare & operate
A shared understanding of updates.
Understand what to review, what to protect and who owns the operating decisions around an EzePanel update.
Update policy under review
- Release information
- Operator preparation
- Verification
- Support
Use approved information for the selected release.
Installation and update guidance must be read with the release’s compatibility information and changes. Source-history entries describe development changes; they do not alone establish a production distribution channel.
Get the current versioned installer in your customer portal. Consult release-specific compatibility and update instructions; no long-term-support period is promised here.
Treat security-related changes as operational work.
Review the available release information for security-relevant changes and assess their significance for your environment. Plan an appropriate maintenance and verification process with the responsibilities of your hosting service in mind.
This page does not promise a fixed security-patch schedule, response-time SLA or automatic remediation of every issue. Use Responsible Disclosure to report a suspected product vulnerability through the approved contact route.
The operator owns the hosting environment.
Keep operating-system changes, application updates and panel updates distinct. An EzePanel release does not establish compatibility for every customer plugin, PHP extension or third-party service.
Completion includes checking the result.
After an update, verify the panel and the services you provide. Review failures and warnings rather than assuming that successful code activation proves customer applications are healthy.
Where recovery is required, use the supported process for the exact transition and available backup material. Restoring old state can affect changes made since the update. Contact support when the release state or recovery path is unclear.
Clear next steps
Questions about responsibility.
Understand the current scope before planning your next step.
Is there an announced long-term-support window?
No fixed support period is established here. Version lifecycle commitments will be published when approved.
Does this policy promise automatic updates?
No. Use the supported release-specific update process and operator controls.
Who verifies hosted applications after an update?
The hosting operator should verify the services and workloads it provides, using the applicable release guidance.
Is a panel update an operating-system upgrade?
No. They are separate changes with different compatibility and recovery requirements.
Continue with EzePanel