Release channels
Stable
The current generally available major version. This is the channel we recommend for production. Stable receives weekly patch releases containing critical bug fixes and security patches only. No new features, data migrations, or infrastructure changes land on stable between major versions. At any given time, the latest major version (N) is the preview channel and the previous major version (N-1) is stable.Preview
The development build of the next major version. Preview includes new features and fixes as they merge into LangSmith SaaS, giving you an early look at what the next major version will contain. Preview builds may include data migrations, but never add or remove services or introduce breaking changes. Preview is intended for evaluation in test and staging environments. We don’t recommend running preview in production.Release cadence
| Channel | Cadence |
|---|---|
| Preview | Published mirroring the LangSmith SaaS release cadence |
Stable — new major (v0.X.0) | Approximately every 6 weeks (two per quarter) |
Stable — patch (v0.X.Y) | Weekly (typically Friday), skipped if no changes. Ad-hoc releases issued for critical customer issues. |
What ships in each channel
| Preview | Stable patch | Next major | |
|---|---|---|---|
| New features | yes | no | yes |
| Bug fixes | yes | critical only | yes |
| Security patches | yes | yes | yes |
| Data migrations and backfills | yes | no | yes |
| New or removed services | no | no | yes |
| Breaking changes | no | no | yes |
Version numbering
Self-hosted LangSmith uses the following scheme:v0.X.0— Major version (stable GA release)v0.X.Y— Stable patch release (critical fixes only)v0.X.0-rcN— Preview build (release candidate) for the next major version, whereNis an incrementing build number
Recommendations
- Run stable in production. Preview is for evaluation only and may contain unreleased features still under validation.
- Use preview in test or staging. Running preview in a non-production environment is the best way to catch issues early and prepare for the next major upgrade.
- Plan for major upgrades. Data migrations, service additions or removals, and breaking changes only land in new major versions. Review the self-hosted changelog before upgrading and plan for any required data or infrastructure changes.
- Stay on a supported version. We recommend upgrading to each new major version soon after it’s released to pick up architectural improvements on our recommended cadence.
Current version
To check the current stable and preview versions, refer to the self-hosted changelog.Connect these docs to Claude, VSCode, and more via MCP for real-time answers.