{"token_count": 1484}

# Teleport Upcoming Releases

Teleport releases a new major version once per year, and provides security-critical support for the current and previous major version. We support each major version for 24 months.

The most recent major version of Teleport, referred to as the **current version**, is the only major version of Teleport that will receive new features. The previous major version, referred to as the **stable version**, will only receive bug fixes and security patches.

## Teleport

### Supported releases

We continue to support the following major versions of Teleport:

| Version | Release | Release Date      | EOL         | Minimum `tsh` version |
| ------- | ------- | ----------------- | ----------- | --------------------- |
| Current | v18.x   | July 3, 2025      | August 2027 | v17.0.0               |
| Stable  | v17.x   | November 16, 2024 | August 2026 | v16.0.0               |

### Upcoming releases

We plan to release the following versions in the coming months:

| Version | Date                       |
| ------- | -------------------------- |
| 18.10.0 | Week of July 6, 2026       |
| 18.11.0 | Week of August 3, 2026     |
| 19.0.0  | Week of September 14, 2026 |

### 18.10.0

#### Directory sharing enhancements for Windows desktop access

Teleport will support sharing multiple directories in a single RDP session. In addition, users will be able to unmount shared directories without terminating the session.

#### Windows sessions summaries

Identity Security will support AI summarization for Windows desktop access session recordings.

### 18.11.0

#### Audit Log Reliability Improvements

Teleport will improve audit log stability and durability in the face of failure scenarios like control plane, networking issues and agent restarts.

#### Agentic UX for Access Configuration

Teleport will provide a custom agent skill for configuring access to connected resources using access lists.

#### Linux Desktop Access

Teleport will support remote desktop sessions to Linux hosts.

*Delayed from Teleport 18.10.0.*

### 19.0.0

#### Amazon Aurora DSQL Cluster State Backend

Teleport will support using Amazon Aurora DSQL as a backend for cluster state.

#### Improved Principal Selection for Access Requests

Teleport will improve access requests experience by allowing users to pick specific principals for SSH nodes, Kubernetes clusters, databases and Windows desktop to better support scenarios like just-in-time access elevation requests.

#### In-band Per-Session MFA for SSH and Desktops

Added in-band MFA for SSH and Desktop sessions, moving MFA checks into session establishment so challenges are bound to the specific session. This removes per-session MFA SSH certificates and reduces MFA bypass risk.

## Teleport Cloud

The key deliverables for Teleport Cloud in the next quarter:

| Week of       | Description                                                     |
| ------------- | --------------------------------------------------------------- |
| June 29, 2026 | Teleport 18.9.0 will begin rollout on Cloud.                    |
| July 06, 2026 | Teleport 18.9.0 agents will begin rollout to eligible tenants.  |
| June 13, 2026 | Teleport 18.10.0 will begin rollout on Cloud.                   |
| July 20, 2026 | Teleport 18.10.0 agents will begin rollout to eligible tenants. |

## Production readiness

Teleport follows [semantic versioning](https://semver.org) for pre-releases and releases.

### Pre-releases

Pre-releases of Teleport (versions with suffixes like `-alpha`, `-beta`, `-rc`) should not be run in production environments.

Pre-releases of Teleport are great for testing new features, breaking changes, and backwards incompatibility issues either in development or staging environments.

### Major Releases

Major releases look like `18.0.0`.

Major releases of Teleport contain many large new features and may contain breaking changes.

Due to the scope and quantity of changes in a major release, we encourage deploying to staging first to verify your usage pattern has not changed.

### Minor Releases

Minor releases look like `18.X.0`.

Minor releases of Teleport typically contain smaller features and improvements. Minor releases can typically be deployed directly to production.

Most customers upgrade to the next major version of Teleport during the first minor release, such as 18.1.0.

### Patch Releases

Patch releases contain small bug fixes and can typically be deployed directly to production.

## Version compatibility

Teleport uses [Semantic Versioning](https://semver.org/). Version numbers include a major version, minor version, and patch version, separated by dots. When running multiple `teleport` binaries within a cluster, the following rules apply:

- Servers support clients that are one major version behind, but do not support clients that are on a newer major version. For example, an 17.x.x Proxy Service instance is compatible with 16.x.x agents and 16.x.x `tsh`, but a 17.x.x agent will not work with an 16.x.x Proxy Service instance. This also means you must not attempt to upgrade from 16.x.x straight to 18.x.x. You must upgrade to 17.x.x first.
- Proxy Service instances and agents do not support Auth Service instances that are on an older major version, and will fail to connect to older Auth Service instances by default. For example, an 18.x.x Proxy Service or agent is not compatible with an 17.x.x Auth Service.
- Auth Service instances should always be the first component of the cluster that is upgraded, and you must upgrade all Auth Service instances to the target version before proceeding to upgrade Proxy Service instances, other agents, and client tools (tsh, tctl, tbot, Connect, etc).