When CircleCI releases new Server versions your team may want to upgrade to the latest release which might introduce some changes that your team were looking forwarding to implementing in your server environment. With the minor and patch versions receiving somewhat frequent updates, it can be less than clear on the optimal upgrade path.

When upgrading your CircleCI Server, you cannot skip any minor releases as there may be migrations that need to be done. When you are on an x.x.0 patch release, you may skip to the latest patch release of that same minor version.


Upgrading your Version and Suggested Upgrade Examples

The path taken for upgrading is dependent on both the currently available versions and releases as well as the current version your team's cluster is on. Some popular upgrade paths can be found below:



From Server 4.0.1 to 4.1.8

4.0.1 > 4.0.6 > 4.1.8
  • While the 4.0.x patches can be skipped, it is recommended to stop at the last patch 4.0.6 


From Server 4.0.6 to 4.1.8

 4.0.6 > 4.1.8
  • Since this is the latest patch for 4.0.x, it can be upgraded right to 4.1.8 before moving onto to 4.1.8


From Server 4.3.0 to 4.3.3

4.3.0 > 4.3.3
  • When upgrading from 4.3.0 release to the latest patch release, 4.3.1 and 4.3.2 can be skipped by upgrading to the latest patch of 4.3.x

If your team has any further questions on these, please do not hesitate to reach out to us on the CircleCI Support Engineering team and we will be happy to confirm the best path for your team to take!

Additional Notes

  • Minor Versions cannot be skipped

    • 4.0.6 --> 4.2.4 is not recommended

  • Patch versions can sometimes be skipped

    • 4.1.8 --> 4.2.4 is possible

Additional Resources

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.