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.
We do not recommend skipping releases when upgrading. However, certain patch versions may be skipped.
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:
4.0.1 > 4.0.4 > 4.1.0 > 4.1.3
- While the
4.0.3patches can be skipped, it is recommended to stop at the last patch
4.0.4before the next minor version (i.e.
4.0.4 > 4.1.0 > 4.1.3
- Since this is the latest patch for
4.0.x, it can be upgraded right to
4.1.0before moving onto to
4.1.0 > 4.1.3
- When upgrading from
4.1.0release to the latest patch release,
4.1.2can be skipped by upgrading to the latest patch of
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!