Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this BEFORE copying the newer version's files over.
Note: 2025.3.1 and higher have important changes to how files are stored on disk that makes them backwards-incompatible with earlier versions. See the release notes for 2025.3.1 for more details.
Changes:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this BEFORE copying the newer version's files over.
Note: 2025.3.1 and higher have important changes to how files are stored on disk that makes them backwards-incompatible with earlier versions. See the release notes for 2025.3.1 for more details.
Changes:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this BEFORE copying the newer version's files over.
Major new features:
We've significantly changed how we store files on disk in this version. Files are no longer stored according to the project they reside in, meaning they no longer need to be moved around when moving files between projects. This has the most benefit on the cloud, but will also speed up large transfers for self-hosting too. The two versions are designed to co-exist - all new uploads will use the new format and existing files will remain in the old format but will be upgraded if moved between projects.
This does of course make it harder to downgrade to an older version, so we have provided a tool in the Admin Area to downgrade your files to the older format before reverting back to an earlier version.
Other changes:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this BEFORE copying the newer version's files over.
Changes:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this BEFORE copying the newer version's files over.
Changes:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this BEFORE copying the newer version's files over.
Changes:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this BEFORE copying the newer version's files over.
Changes:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this BEFORE copying the newer version's files over.
Changes:
Changes since Beta 3:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this BEFORE copying the newer version's files over.
Note: This release is a beta version. Although it has been extensively tested, we have given it a beta label due to the major changes it contains. You should therefore be cautious before rolling it out to a production server.
Changes since Beta 2:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this BEFORE copying the newer version's files over.
Note: This release is a beta version. Although it has been extensively tested, we have given it a beta label due to the major changes it contains. You should therefore be cautious before rolling it out to a production server.
Changes since Beta 1:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this BEFORE copying the newer version's files over.
Note: This release is a beta version. Although it has been extensively tested, we have given it a beta label given the major changes it contains. You should therefore be cautious before rolling it out to a production server.
Changes:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this before copying the newer version's files over.
Changes:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this before copying the newer version's files over.
Changes:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this before copying the newer version's files over.
Note: Due to the need to build caches, the upgrader may take a while to run if you have a large number of projects and/or a large number of files.
Changes:
Important: The Docker image is configured to convert the current database to your MariaDB version automatically. As such, we would recommend backing up the database before upgrading to any version as you may be unable to downgrade otherwise. You can download the current database as a .sql file from the Tools section of the Admin Area. We recommend doing this before copying the newer version's files over.
Changes:
Changes: