Teleport Upcoming Releases
Teleport releases a new major version approximately every 4 months, and provides security-critical support for the current and two previous major versions. With our typical release cadence, we usually support each major version for 12 months.
Teleport
We plan to release the following versions in the coming months:
| Version | Date |
|---|---|
| 17.5.0 | Week of May 19, 2025 |
| 18.0.0 | Week of May 26, 2025 |
| 18.1.0 | Week of June 16, 2025 |
We continue to support the following major versions of Teleport:
| Release | Release Date | EOL | Minimum tsh version |
|---|---|---|---|
| v17.x | November 16, 2024 | January 2026 | v16.0.0 |
| v16.x | June 14, 2024 | September 2025 | v15.0.0 |
| v15.x | January 29, 2024 | May 2025 | v14.0.0 |
17.5.0
Azure Console via SAML IdP
Teleport SAML IdP will support Azure web console as a service provider.
Desktop Access in Teleport Connect
Teleport Connect will allow users to connect to Windows desktops directly from the Teleport Connect application without needing to use a browser.
VNet for SSH
Teleport VNet will add native support for SSH, enabling any SSH client to connect to Teleport SSH servers with zero configuration. Advanced Teleport features like per-session MFA will have first-class support for a seamless user experience.
Desktop Access latency detector
Teleport's web UI will show latency measurements during remote desktop sessions which indicate both the latency between the user and the Teleport proxy as well as the latency between the Teleport proxy and the target host.
18.0.0
Identity Activity Center
Teleport Identity Security (fka Teleport Policy) will provide an Identity Activity Center to allow users to correlate user activity by multiple factors to facilitate incident response. The first iteration will support integrations with GitHub, Okta and AWS.
Automatic access request reviews
Teleport will provide the ability to perform automatic access request reviews based on requested roles out of the box.
Multi-session MFA for Database Access
Teleport will provide a more user-friendly way to execute queries on multiple databases when per-session MFA is enabled, without requiring MFA tap for each connection.
RBAC for SAML applications
Users will be able to control access to SAML applications using role labels similar to other Teleport-protected resources.
18.1.0
Encrypted session recordings
Teleport will provide the ability to integrate with Hardware Security Modules (HSMs) in order to encrypt session recordings prior to uploading them to storage.
Teleport Cloud
The key deliverables for Teleport Cloud in the next quarter:
| Week of | Description |
|---|---|
| May 26, 2025 | Teleport 17.5 will begin rollout on Cloud. |
| May 26, 2025 | Teleport 17.5 agents will begin rollout to eligible tenants. |
Production readiness
Teleport follows semantic versioning 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 16.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 16.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 16.1.0.
Patch Releases
Patch releases contain small bug fixes and can typically be deployed directly to production.
Version compatibility
Teleport uses Semantic Versioning. 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 8.x.x Proxy Service
instance is compatible with 7.x.x agents and 7.x.x
tsh, but we don't guarantee that a 9.x.x agent will work with an 8.x.x Proxy Service instance. This also means you must not attempt to upgrade from 6.x.x straight to 8.x.x. You must upgrade to 7.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 8.x.x Proxy Service or agent is not compatible with an 7.x.x Auth Service.