Keeping Exponential current after adoption
Contents
Why it matters
Security fixes are made on main and "published with the next 6.0.x release"; "a fix for a problem in v6.0.14 or an
earlier tag reaches you as the next release, not as a corrected copy of the old one" (SECURITY.md). A site that
does not update does not get fixes.
How releases reach you
- Through Composer or Git, depending on how the site was installed (Update with Git).
- Setup > Updates and packages in the administration finds and installs Composer packages (Roadmap).
- What changed: the changelogs (Staying informed).
A routine
| When | Do |
|---|---|
| Monthly | Check for new releases and read their notes |
| Within days of a security release | Apply it, first on staging |
| Each update | Follow the upgrade day checklist |
| Yearly | Check the PHP version and the extensions |
How updates work for owners: How updates work. With a provider: Upgrades with your provider.
Extensions and PHP
- Each extension has its own releases (How packages are versioned).
- Keep PHP on a supported version: Exponential runs on 8.0 to 8.5 (
README.md). - Custom code kept in extensions makes updates easier (Extending without forking).
Related pages
- After adoption
- Release line and support
- Upgrades without surprises
- Upgrading
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.