Skip to content

Versioning and the release process#

We use semantic versioning (SemVer) for releases.

Frequency#

Recent releases came about every two to three months: 1.8.0 in May 2026, 1.9.0 in July 2026, and 2.0.0 in October 2026. The releases page lists all releases.

Version numbers#

Autoware has its own version number

The Autoware version does not follow the version of autoware_core or of any other sub-repository. For example, Autoware 2.0.0 uses autoware_core 1.10.0. From Autoware 1.5.0 to 1.9.0, the Autoware version was the same as the autoware_core version. The one exception is the patch release 1.7.1, which uses autoware_core 1.7.0.

Each sub-repository tracks its own version. The repositories/autoware.repos file at each Autoware release tag records the version of each sub-repository. In Autoware 1.5.0 and earlier releases, this file is autoware.repos at the root of the repository.

The release process#

Autoware has many repositories that must work together. A release follows these steps:

  1. Release the sub-repositories. We release all the required sub-repositories, such as autoware_core and autoware_universe. A repository that did not change keeps its existing version.
  2. Update the references. We update the versions of the sub-repositories in the repositories/autoware.repos file.
  3. Test the system. We test the system manually in the simulations, and we make sure that the CI for the build passes.
  4. Release Autoware. We make the Autoware release.

Patches#

If a critical bug needs a fix, we make a patch release of the affected repositories. Then we make a patch release of Autoware.