The MariaDB Foundation has officially released the stable version of MariaDB 13.0, completing a lengthy testing and refinement process that began with its initial preview. This update focuses on enhancing the database's expressiveness, observability, and ease of troubleshooting. It particularly emphasizes compatibility with advanced procedural SQL and provides improved tools for database administrators. A major highlight of this release is the integration of DuckDB, which expands MariaDB's capabilities to include more advanced analytical processing alongside its traditional transactional functions. MariaDB is an open-source relational database management system (RDBMS) that originated as a fork of MySQL in 2009. This happened after Oracle Corporation acquired Sun Microsystems, which had originally developed MySQL. The original developers created MariaDB to ensure MySQL would remain free and open-source under the GNU General Public License. Initially intended as a direct replacement for MySQL, the two databases have since evolved with different features, syntax, and behaviors. Over more than sixteen years of independent development, MariaDB has grown into a versatile system that supports transactional, analytical, and even AI-related workloads. The MariaDB Foundation, a non-profit organization, oversees the open-source development of MariaDB independently of any commercial interests. The latest stable version of MariaDB 13 includes improved SQL compatibility, new InnoDB features, and the DuckDB integration. It also includes security patches for vulnerabilities identified through MariaDB's HackerOne bug bounty program. While specific details about these vulnerabilities are not disclosed, this is to prevent potential misuse before users can update their systems. The release of MariaDB 13.0 follows a continuous release model, which allows users to access the latest SQL features and engine improvements without waiting for long-term support (LTS) versions. Although labeled as "stable," this version does not receive the extended maintenance period that LTS versions do, which are typically recommended for environments that prioritize stability and slower update cycles. The transition from preview to stable status indicates that the features have reached a mature and reliable state, though some features like optimizer tracing and atomic CREATE OR REPLACE TABLE commands are still under development. The release process also involves extensive review of security reports, testing of fixes, and ensuring no new issues are introduced. This work is crucial but often less visible than new feature announcements.