Upgrade
A full changelog of past releases is available on GitHub Releases page.
Before performing a Certimate upgrade, it is recommended to back up all data to prevent any issues during the upgrade process.
Read the Backup and Restore guide to learn more details.
Upgrade process
Via binary Installation
- Stop the old version process.
- Backup Certimate data.
- Download the new version release and replace the files in your installation directory.
- Restart Certimate.
Via Docker Installation
docker compose down
ordocker stop
to stop the old version container.- Backup Certimate data.
docker compose pull
ordocker pull
to pull the new image.docker compose up -d
ordocker run
to restart the container.
Cross version upgrades
You can skip multiple minor versions to upgrade directly under the same major version (such as v0.3.0 → v0.3.5), and Certimate will automatically migrate your application data.
When you try to skip some major versions (such as v0.2.15 → v0.3.0), you need to follow the precautions in the migration guide.
It is not recommended to skip multiple major version upgrades in a row. You should perform the upgrade in order of the major version number (such as v0.1.9 → v0.2.0 → v0.3.0 → v0.3.5).
Read the Releases and the Migrations guide to learn more details.
Downgrade
Unfortunately, once the upgrading is completed, it is no longer supported to rollback, as the data structure may have undergone fundamental changes.
Therefore, please do not forget to back up your old version data!