Release Notes
Versioning Scheme
Maravelith and its other first-party packages follow Semantic Versioning. Major framework releases are released every 2 years (~Q4), while minor and patch releases may be released as often as every week. Minor and patch releases should never contain breaking changes.
When referencing the Maravelith framework or its components from your application or package, you should always use a version constraint such as ^20.0, since major releases of Maravelith do include breaking changes. However, we strive to always ensure you may update to a new major release in one day or less.
Named Arguments
Named arguments are not covered by Maravelith’s backwards compatibility guidelines. We may choose to rename function arguments when necessary in order to improve the Maravelith codebase. Therefore, using named arguments when calling Maravelith methods should be done cautiously and with the understanding that the parameter names may change in the future.
Support Policy
For Maravelith releases, bug fixes and security fixes are provided for 3 years. In addition, please review the database versions supported by Maravelith.
| Version | PHP (*) | Release | Bug Fixes Until | Security Fixes Until |
|---|---|---|---|---|
| 10 | 8.1 - 8.4 | 2025 | 30 Nov 2027 | 30 Nov 2027 |
| 20 | 8.2 - 8.4 (8.5 Beta) | Q4 2026 | 30 Nov 2029 | 30 Nov 2029 |
(*) Supported PHP versions
Maravelith 20
Maravelith 20 represents a massive leap forward in architectural performance, memory efficiency, and modernization. In this release, the framework has been strictly aligned with modern PHP standards and optimized for high-speed execution environments. \
By decoupling heavy dependencies, introducing a custom high-performance Request hydration engine, and deeply optimizing the core Service Container, Maravelith 20 delivers our leanest, fastest, and most robust backend experience to date.
Next-Generation Service Container
The underlying Service Container has received a massive, ground-up rewrite. Maravelith 20 introduces Two-Tier DI Caching with encapsulated cache loading and deep OPcache protection. \
By shifting legacy properties to a flat-array structure and fusing the JSON request bag directly into the primary InputBag, the container drastically reduces its baseline memory footprint. The container’s relay logic is now completely stateless, ensuring your application remains highly performant even under extreme load.