Skip to main content
Understanding the Gogs release strategy helps you plan upgrades safely and avoid breaking changes.

​
Semantic versioning

Starting with version 0.12.0, Gogs follows semantic versioning. Version numbers use the format MAJOR.MINOR.PATCH: Each minor release has its own release branch with the prefix release/. For example, release/0.12 is the branch for version 0.12.0 and all of its patch releases (0.12.1, 0.12.2, and so on).

​
Backwards compatibility

​
Upgrading from versions before 0.12

If you are running any version of Gogs below 0.12, you must first upgrade to 0.12 before upgrading further. This version includes essential database migrations that later versions depend on.

​
Upgrading from 0.12 and later

Gogs maintains backwards compatibility across one minor version at a time. Patch release numbers are disregarded when determining compatibility. Supported upgrade paths:
Always upgrade one minor version at a time. For example, to go from 0.12 to 0.14, first upgrade to 0.13, verify everything works, and then upgrade to 0.14.

​
Source build update frequency

If you run Gogs from a source build rather than an official binary, update at least once per week. This prevents you from falling behind and potentially missing incremental database migrations that cannot be applied out of order.