# A backward-compatibility window for the CLI

**URL:** <https://community.tuist.dev/t/a-backward-compatibility-window-for-the-cli/992>\
**Category:** Announcements\
**Created:** [June 8, 2026, 2:54pm UTC](https://community.tuist.dev/t/a-backward-compatibility-window-for-the-cli/992 "2026-06-08T14:54:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![marekfort](https://community.tuist.dev/user_avatar/community.tuist.dev/marekfort/32/8_2.png) [@marekfort](https://community.tuist.dev/u/marekfort)\
**Post date:** [June 8, 2026, 2:54pm UTC](https://community.tuist.dev/t/a-backward-compatibility-window-for-the-cli/992/1 "2026-06-08T14:54:15Z")

</div>

The Tuist server ships continuously, independently of when you upgrade the CLI. To prevent regressions when new server versions would break older CLI versions, we now run our acceptance test suite against the oldest support CLI version on every deploy.

## What’s new

We support every CLI release from the last 3 months (right now, the oldest CLI version we officially support is `4.150.0`). Within that window, server changes stay backward compatible, so you can upgrade on your own schedule.

Every production deploy is now gated on an acceptance test against the oldest supported release, so we catch any break before it reaches you.

A new [Compatibility page](https://tuist.dev/en/docs/cli/compatibility) documents the policy.

## Do I need to do anything?

If you’re on a release from the last 3 months, no. Older versions are considered deprecated and may prompt you to upgrade, so bumping the CLI at least quarterly keeps you supported.

Learn more:

Compatibility policy: [Compatibility · CLI · Tuist](https://tuist.dev/en/docs/cli/compatibility)  
Pull request: [feat(server): gate production on an oldest-supported-CLI acceptance suite by fortmarek · Pull Request #11097 · tuist/tuist · GitHub](https://github.com/tuist/tuist/pull/11097)