Skip to content
Coder Docs

Releases

Learn about Coder's release channels, versioning, and schedule so you can plan upgrades.

On this page

Coder releases are cut directly from the main branch of the coder/coder repo. For a full list of releases, you can visit coder/coder's Releases. Alternatively, if you just want the latest CLI, you can visit the Coder Downloads page.

This page explains details about our release versioning scheme, schedules, terminology, and support periods.

We recommend enterprise customers test the compatibility of new releases with their infrastructure on a staging environment before upgrading a production deployment.

Release versioning

Coder releases follow a semantic versioning scheme. Each release takes the format vX.Y.Z:

  • X is the major version. The current major version of Coder is 2.
  • Y is the minor version. The docs will also refer to the minor version as the combined vX.Y.
  • Z is the specific release, also referred to as the hotfix or patch release for a given minor version.

The Coder Team handles releasing minor versions differently from releasing patches. This section includes details on each.

Minor versions

Generally, the Coder Team publishes new minor versions on the first Tuesday of every month. The release of a new minor version is always patch release 0 (for example, vX.Y.0). The date of a .0 release for a given minor version is the same as a minor version's release date.

January releases

Minor versions on the first Tuesday of January are not guaranteed to occur, due to limited availability of the Coder Team during the December holiday season. However, an ad-hoc release might still occur. Do not rely on the availability of a January minor release. If needed, reach out to Coder Support or your account team directly to determine if one will be occurring closer to the release date.

Patch releases

The Coder Team ships bug fixes and security patches between minor releases as patch releases, such as v2.38.5. Patch releases don't follow a fixed schedule. That being said, each minor version, on average, has a new patch release about once a week.

A patch release becomes unsupported when a newer patch release on the same minor version is published. This means that you should apply the latest patch release to your Coder deployment to get the latest bug fixes and security patches. The Coder Support Team may ask you during troubleshooting to apply the latest patch release as a troubleshooting step.

To request a patch release for an issue that affects your deployment, contact Coder support with your Coder version, the impact, and any deadline. To test a fix before it's released, use the preview image described in Release schedule.

Fixes are backported to the release branches that are eligible for them:

Release channelBackported fixes
MainlineBug fixes and security patches
StableBug fixes and security patches
Security SupportSecurity patches and CVE fixes
Extended Support ReleaseCritical bug fixes and security patches

The Coder Team decides which releases receive a bug fix based on its severity and how likely users on each release are to encounter the bug. A fix might ship only in mainline and stable, in which case the supported path for older releases is to upgrade to a supported release.

Fixes that require a database schema change aren't backported. They ship in the next minor release.

Release channels

Coder ships in four primary release channels:

  • Mainline
  • Stable
  • Security Support
  • Extended Support Release

Coder also occasionally ships release candidates (RCs), which are ad-hoc builds meant to validate in-development features. RCs are separate from the four primary channels and are described below.

The Coder Team launches each new minor version as mainline at release time and promotes it to stable after one month. The security support version receives patches only for security issues or Common Vulnerabilities and Exposures (CVEs).

Mainline releases

The bleeding edge version of Coder. This is also whichever version has the latest .0 release. Mainline releases:

  • Are intended for customers with a staging environment.
  • Gives earliest access to new features.
  • Might include minor bugs.
  • Will include all bug fixes and security patches.

Stable releases

The minor version before the mainline version. If the mainline version is Y, then the stable version is Y - 1. Stable releases:

  • Are the safest upgrade/installation path.
  • Might not include the latest features.
  • Will include all bug fixes and security patches.

Security Support

The minor version before the stable version. If the mainline version is Y, then the security support version is Y - 2. Security releases:

  • Might not include the latest features.
  • Do not receive bug fixes except for in-product security vulnerabilities and CVEs.
  • Are not recommended for new deployments.
  • Will reach support end of life (EOL) after one month, unless it is an Extended Support Release.

For more information on feature rollout, visit the feature stages documentation.

Extended Support Release

Two releases each year are designated as Extended Support Releases (ESRs). Each ESR is supported for 12 months from the date of its .0 release. ESRs:

  • Are designed for organizations that prioritize long-term stability.
  • Receive only critical bug fixes and security patches.
  • Are ideal for regulated environments or large deployments with strict upgrade cycles.

ESR versions will be updated with critical bug fixes and security patches that are available to paying customers. This extended support model provides predictable, long-term maintenance for organizations that require enhanced stability. Because ESR forgoes new features in favor of maintenance and stability, it is best suited for teams with strict upgrade constraints. The latest ESR version is Coder 2.34.

For more information, visit the Coder ESR announcement or the 2.29 to 2.34 ESR Upgrade Guide.

Release Candidates

Release Candidates (RCs) are ad-hoc builds that Coder releases to validate in-development features with select customers. Features introduced in a release candidate (RC) are not guaranteed to be included in a mainline or stable release. RCs:

  • Are not guaranteed to be stable or free of bugs.
  • Are not intended for production use.

With RCs, the Coder Team can create builds for customers and other users to try out new, under-development functionality without cutting a new minor version. Unlike mainline and stable releases, RCs do not follow a fixed schedule and carry no guarantees around stability or long-term support. They exist purely as a feedback mechanism: the Coder Team can ship targeted builds, gather real-world input, and iterate before committing changes to the standard release channels.

Install stable

Download the latest stable or mainline release from the Coder downloads page. To install a specific version, use the coder/coder releases page on GitHub.

You can also use the install.sh script with the --stable flag to install the latest stable release:

curl -fsSL https://coder.com/install.sh | sh -s -- --stable

You can find best practices for installing Coder in the Install section.

Release schedule

Release nameRelease DateStatusLatest Release
2.29December 02, 2025Extended Support Releasev2.29.29
2.34June 02, 2026Extended Support Releasev2.34.21
2.35July 07, 2026Not Supportedv2.35.12
2.36August 04, 2026Not Supportedv2.36.12
2.37September 01, 2026Security Supportv2.37.14
2.38October 06, 2026Stablev2.38.10
2.39November 03, 2026Mainlinev2.39.4
2.40Not ReleasedN/A

Release data from GitHub as of November 17, 2026.

Tip

We publish a preview image ghcr.io/coder/coder-preview on each commit to the main branch. You can use this to test under-development features and bug fixes that have not yet been released to mainline or stable.

The preview image is not intended for production use.