Hosting & Infrastructure

Update & Versioning Policy

How CORA versions work, update cadences, and how changes reach client sites.

Version numbering

• 1.0 — Major release: New features or breaking changes. Manual update, full QA cycle before release.
• 1.1 — Feature update: New non-breaking functionality. Manual update, tested on staging first.
• 1.1.1 — Security patch: Critical security fixes. Can be deployed automatically. Infrastructure lead notified.

The annual theme release follows a year-based convention: CORA 2026, CORA 2027, etc.

Update cadence

• Third-party plugins: Minor updates run daily via SPM
• Major plugin updates (e.g. page builders): Manual, tested on staging first
• CORA feature releases (x.1–x.9): 2-week sprint cycle
• CORA major versions (x.0): Annual or as needed
• Security patches (x.x.1): Deployed as needed, can be automatic

How updates reach client sites

CORA updates are delivered as plugin updates — the same mechanism WordPress uses for any plugin.

1. New version appears in WordPress admin under Plugins → Updates
2. Vital’s hosting and maintenance team applies to staging first
3. After QA sign-off, pushed to production
4. Sites on CORA Cloud hosting have this entire process managed by Vital

QA process

Every non-patch release goes through a QA cycle:

• Feature testing on dev.coraweb.com
• Regression testing on industry demo sites
• Staging deployment to one or more client sites for real-world validation
• Technical lead sign-off before production push