# MariaDB version numbers
<a name="USER_UpgradeDBInstance.MariaDB.VersionID"></a>

The version numbering sequence for the RDS for MariaDB database engine is either in the form of *major.minor.patch.YYYYMMDD* or *major.minor.patch*, for example, 10.11.5.R2.20231201 or 10.4.30. The format used depends on the MariaDB engine version.

**major**  
The major version number is both the integer and the first fractional part of the version number, for example, 10.11. A major version upgrade increases the major part of the version number. For example, an upgrade from *10.5*.20 to 10.6.12 is a major version upgrade, where *10.5* and *10.6* are the major version numbers.

**minor**  
The minor version number is the third part of the version number, for example, the 5 in 10.11.5.

**patch**  
The patch is the fourth part of the version number, for example, the R2 in 10.11.5.R2. An RDS patch version includes important bug fixes added to a minor version after its release.

**YYYYMMDD**  
The date is the fifth part of the version number, for example, the 20231201 in 10.11.5.R2.20231201. An RDS date version is a security patch that includes important security fixes added to a minor version after its release. It doesn't include any fixes that might change an engine's behavior.

The following table explains the naming scheme for RDS for MariaDB version 10.11. 


| 10.11 minor version | Naming scheme | 
| --- | --- | 
| ≥5  | New DB instances use *major.minor.patch.YYMMDD*, for example, 10.11.5.R2.20231201. Existing DB instances might use *major.minor.patch*, for example, 10.11.5.R2, until your next major or minor version upgrade. | 
| < 5 |  Existing DB instances use *major.minor.patch*, for example, 10.11.4.R2.  | 

The following table explains the naming scheme for RDS for MariaDB version 10.6. 


| 10.6 minor version | Naming scheme | 
| --- | --- | 
| ≥ 14 |  New DB instances use *major.minor.patch.YYMMDD*, for example, 10.6.14.R2.20231201. Existing DB instances might use *major.minor.patch*, for example, 10.6.14.R2, until your next major or minor version upgrade. | 
| < 14 | Existing DB instances use *major.minor.patch*, for example, 10.6.13.R2. | 

The following table explains the naming scheme for RDS for MariaDB version 10.5. 


| 10.5 minor version | Naming scheme | 
| --- | --- | 
| ≥ 21 |  New DB instances use *major.minor.patch.YYMMDD*, for example, 10.5.21.R2.20231201. Existing DB instances might use *major.minor.patch*, for example, 10.5.21.R2, until your next major or minor version upgrade. | 
| < 21 |  Existing DB instances use *major.minor.patch*, for example, 10.5.20.R2.  | 

The following table explains the naming scheme for RDS for MariaDB version 10.4. 


| 10.4 minor version | Naming scheme | 
| --- | --- | 
| ≥ 30 |  New DB instances use *major.minor.patch.YYMMDD*, for example, 10.4.30.R2.20231201. Existing DB instances might use *major.minor.patch*, for example, 10.4.30.R2, until your next major or minor version upgrade. | 
| < 30 |  Existing DB instances use *major.minor.patch*, for example, 10.4.29.R2.  |