How do I keep self-hosted software up to date?

Follow the vendor’s release notes and security advisories, test supported upgrade paths outside production, and automate the reviewed procedure where practical. Set a maximum version lag and a recovery plan for failed upgrades. Directory updates supplement the vendor’s own channels.

Keep a release and support record

Record the installed application, deployment chart or operator, database and relevant component versions separately. Follow vendor release notes, supported upgrade sequences and security advisories. A current directory review date means sources were reviewed; it does not mean your installation is current.

Rehearse state changes

Use a representative non-production copy to test migrations, changed settings, identity behavior and connected services. Confirm backup validity and a supported recovery path before applying an upgrade that changes stored state. Rolling back an image is not necessarily enough to reverse a database migration.

Assign an owner and an allowed version lag, with a separate process for urgent fixes. The directory’s watch tools and feeds report editorial changes and reviewed advisory information within their scope. Keep subscribing to the vendor’s own security and end-of-life channels rather than relying on a directory feed alone.

Sources and further guidance

Answer reviewed 2026-11-21. Check the exact edition, configuration and current vendor terms before deciding.

All 50 questions · Deployment guide · Build a shortlist